@exaudeus/memory-mcp 0.1.0

package/dist/__tests__/ephemeral-benchmark.test.js

@@ -0,0 +1,651 @@
+// Ephemeral detection benchmark — measures precision/recall of the signal registry.
+//
+// 200+ labeled test cases: ephemeral (should warn) + durable (should not warn).
+// Run with: npm test -- --test-name-pattern "ephemeral benchmark"
+//
+// The benchmark produces a confusion matrix:
+//   TP = ephemeral entry correctly warned
+//   FP = durable entry incorrectly warned (false alarm)
+//   FN = ephemeral entry missed (no warning)
+//   TN = durable entry correctly not warned
+//
+// Precision = TP / (TP + FP)  — "when we warn, are we right?"
+// Recall    = TP / (TP + FN)  — "do we catch all ephemeral content?"
+import { describe, it } from 'node:test';
+import assert from 'node:assert';
+import { detectEphemeralSignals } from '../ephemeral.js';
+// ─── EPHEMERAL CASES (should produce at least one signal) ─────────────────
+const EPHEMERAL_CASES = [
+    // -- Temporal language (12 cases) --
+    { title: 'Build Status', content: 'The CI pipeline is currently broken due to a flaky integration test on the messaging module', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['temporal'] },
+    { title: 'Server State', content: 'The dev server is not responding right now, team is looking into it', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['temporal'] },
+    { title: 'API Change', content: 'As of today the v3 endpoint returns a different schema for listing details', topic: 'architecture', label: 'ephemeral', expectedSignals: ['temporal'] },
+    { title: 'Test Flake', content: 'The login test just failed again, this is the third time today', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['temporal'] },
+    { title: 'Workaround', content: 'For now we are using a manual cache clear before each build to avoid the stale artifact issue', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['temporal'] },
+    { title: 'Branch State', content: 'At the moment the feature branch has merge conflicts with main that need resolving', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['temporal'] },
+    { title: 'Temp Fix', content: 'Temporarily disabled the image optimization pipeline because it was causing OOM errors', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['temporal'] },
+    { title: 'Progress', content: 'Migration is ongoing, about 60% of the endpoints have been ported to the new framework', topic: 'architecture', label: 'ephemeral', expectedSignals: ['temporal'] },
+    { title: 'Deployment', content: 'We just noticed that the staging environment has stale certificates after the deployment', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['temporal'] },
+    { title: 'Sprint Status', content: 'The messaging feature is in progress and should be ready for review by end of sprint', topic: 'architecture', label: 'ephemeral', expectedSignals: ['temporal'] },
+    { title: 'Quick Note', content: 'Just discovered that the analytics SDK requires a special initialization on Android 14', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['temporal'] },
+    { title: 'Interim State', content: 'At this point we have three different authentication flows coexisting until the migration completes', topic: 'architecture', label: 'ephemeral', expectedSignals: ['temporal'] },
+    // -- Fixed/resolved bugs (10 cases) --
+    { title: 'Messaging Crash', content: 'The crash in MessagingReducer has been fixed by adding proper null handling for the sender field', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['fixed-bug'] },
+    { title: 'Build Failure', content: 'The Gradle sync issue was resolved by upgrading the AGP plugin to 8.2.1', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['fixed-bug'] },
+    { title: 'Flaky Test', content: 'The flaky coroutine test no longer fails after we added proper scope cancellation in tearDown', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['fixed-bug'] },
+    { title: 'Memory Leak', content: 'The memory leak bug in the image loader was fixed by switching to weak references for the callback', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['fixed-bug'] },
+    { title: 'Login Error', content: 'The login error was broken on Samsung devices but patched in the latest release with a vendor-specific workaround', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['fixed-bug'] },
+    { title: 'Workaround Removed', content: 'The manual cache clearing workaround for Tuist is no longer needed after the 3.2 update', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['fixed-bug'] },
+    { title: 'API Fix', content: 'This used to be a problem with the pagination API but the backend team corrected the offset calculation', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['fixed-bug'] },
+    { title: 'Network Issue', content: 'The timeout error on the search endpoint was resolved after the infrastructure team increased the connection pool', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['fixed-bug'] },
+    { title: 'CI Fix', content: 'The CI pipeline was failing on ARM runners but it works now after updating the Docker base image', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['fixed-bug'] },
+    { title: 'Render Bug', content: 'The layout issue has been addressed by switching from ConstraintLayout to a simpler LinearLayout', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['fixed-bug'] },
+    // -- Task/TODO language (8 cases) --
+    { title: 'Migration Plan', content: 'We need to migrate all the ViewModels from LiveData to StateFlow before the next release', topic: 'architecture', label: 'ephemeral', expectedSignals: ['task-language'] },
+    { title: 'Test Coverage', content: 'TODO: add integration tests for the new messaging flow, especially the edge cases around reconnection', topic: 'conventions', label: 'ephemeral', expectedSignals: ['task-language'] },
+    { title: 'Refactoring', content: 'We should refactor the DI module to use Anvil instead of manual Dagger components', topic: 'architecture', label: 'ephemeral', expectedSignals: ['task-language'] },
+    { title: 'Cleanup', content: 'I will implement the new error handling pattern across all network calls in the messaging feature', topic: 'conventions', label: 'ephemeral', expectedSignals: ['task-language'] },
+    { title: 'Reminder', content: 'Remember to update the ProGuard rules when adding new Kotlin serialization models', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['task-language'] },
+    { title: 'Next Steps', content: 'Next step is to wire up the analytics events for the new messaging compose screen', topic: 'architecture', label: 'ephemeral', expectedSignals: ['task-language'] },
+    { title: 'Planning', content: 'We plan to replace Retrofit with Ktor client for all new networking code going forward', topic: 'architecture', label: 'ephemeral', expectedSignals: ['task-language'] },
+    { title: 'Debt', content: "Don't forget to remove the legacy messaging module once the new one is fully rolled out", topic: 'gotchas', label: 'ephemeral', expectedSignals: ['task-language'] },
+    // -- Investigation language (8 cases) --
+    { title: 'Memory Investigation', content: 'Still investigating why the messaging tab leaks memory when rapidly switching between conversations', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['investigation'] },
+    { title: 'Crash Analysis', content: 'Debugging the ANR that occurs when the app returns from background with an expired auth token', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['investigation'] },
+    { title: 'Performance', content: 'Looking into the scroll jank on the listings feed, profiler shows overdraw in the image composable', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['investigation'] },
+    { title: 'Root Cause', content: 'Trying to figure out why the WebSocket connection drops every 30 seconds on cellular networks', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['investigation'] },
+    { title: 'Unresolved', content: "Haven't determined yet whether the race condition is in the reducer or the middleware", topic: 'gotchas', label: 'ephemeral', expectedSignals: ['investigation'] },
+    { title: 'Debug Session', content: 'Digging into the Compose recomposition issue that causes the entire list to redraw on single item change', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['investigation'] },
+    { title: 'Ongoing Debug', content: 'Still working on reproducing the crash that only happens on Pixel 6 devices with Android 13', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['investigation'] },
+    { title: 'Analysis', content: 'Still figuring out the correct Coroutine scope hierarchy for the new messaging feature architecture', topic: 'architecture', label: 'ephemeral', expectedSignals: ['investigation'] },
+    // -- Uncertainty/speculation (12 cases) --
+    { title: 'Possible Cause', content: 'I think the crash is caused by a race condition between the auth token refresh and the API call', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['uncertainty'] },
+    { title: 'Architecture Guess', content: 'Maybe we should use a shared ViewModel for the messaging tabs instead of separate ones per tab', topic: 'architecture', label: 'ephemeral', expectedSignals: ['uncertainty'] },
+    { title: 'DI Uncertainty', content: 'Not sure if the Anvil scope should be AppScope or ActivityScope for the messaging component bindings', topic: 'conventions', label: 'ephemeral', expectedSignals: ['uncertainty'] },
+    { title: 'Flaky Test Theory', content: 'The intermittent test failure might be because of shared mutable state between test cases in the suite', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['uncertainty'] },
+    { title: 'Memory Hunch', content: 'It seems like the image cache grows unbounded after navigating between property listings repeatedly', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['uncertainty'] },
+    { title: 'Performance Guess', content: 'I suspect the UI jank is coming from the synchronous JSON parsing on the main thread', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['uncertainty'] },
+    { title: 'Design Uncertainty', content: 'Perhaps the better approach is to use a sealed interface for the navigation events instead of an enum', topic: 'architecture', label: 'ephemeral', expectedSignals: ['uncertainty'] },
+    { title: 'Unverified Pattern', content: 'I believe the WebSocket reconnection logic should use exponential backoff but this is not confirmed by the team', topic: 'conventions', label: 'ephemeral', expectedSignals: ['uncertainty'] },
+    { title: 'Speculation', content: 'The OOM could be due to the bitmap pool not being cleared on configuration change, but this is just guessing', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['uncertainty'] },
+    { title: 'Hypothesis', content: 'My hypothesis is that the cold start regression is from the new feature flag initialization running on the main thread', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['uncertainty'] },
+    { title: 'Tentative Conclusion', content: 'Appears to be a problem with the coroutine dispatcher not being injected properly in the test environment', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['uncertainty'] },
+    { title: 'Vague Suspicion', content: 'Probably related to the recent Compose compiler update since the behavior changed after upgrading to 1.5.0', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['uncertainty'] },
+    // -- Stack traces (4 cases) --
+    { title: 'Crash Log', content: 'NullPointerException in messaging:\n  at com.zillow.messaging.MessagingReducer.reduce(MessagingReducer.kt:42)\n  at com.zillow.core.BaseViewModel.dispatch(BaseViewModel.kt:15)', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['stack-trace'] },
+    { title: 'Python Error', content: 'Build script fails with:\nTraceback (most recent call last)\n  File "build.py", line 42, in generate\n    raise ValueError("invalid config")', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['stack-trace'] },
+    { title: 'Node Error', content: 'Server crashes on startup:\nError: Cannot find module "./config"\n  at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1039:15)', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['stack-trace'] },
+    { title: 'Exception Chain', content: 'Auth failure details:\nCaused by: java.net.SocketTimeoutException: connect timed out\n  at java.net.PlainSocketImpl.socketConnect(Native Method)', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['stack-trace'] },
+    // -- Mixed/multi-signal ephemeral (6 cases) --
+    { title: 'Debug Session', content: 'Currently debugging a crash that just happened. I think it might be related to the new auth flow. Stack:\n  at com.zillow.auth.TokenManager.refresh(TokenManager.kt:88)', topic: 'gotchas', label: 'ephemeral' },
+    { title: 'Status Report', content: 'The migration is ongoing and we still need to update the remaining ViewModels. Not sure about the timeline but probably next sprint.', topic: 'architecture', label: 'ephemeral' },
+    { title: 'Quick Fix Note', content: 'Just fixed the build issue by temporarily disabling the lint check. TODO: re-enable after the upstream plugin is patched.', topic: 'gotchas', label: 'ephemeral' },
+    { title: 'Investigation Update', content: "Investigating the memory leak. I suspect it's the image cache but haven't confirmed. The heap dump shows growth in bitmap allocations.", topic: 'gotchas', label: 'ephemeral' },
+    { title: 'Tentative Fix', content: 'Maybe the fix for the race condition is to use a mutex around the shared state. I believe this approach was suggested somewhere but not verified.', topic: 'gotchas', label: 'ephemeral' },
+    { title: 'Temp Workaround', content: 'For now using a hardcoded delay of 500ms before retrying the WebSocket connection. This is probably not the right approach.', topic: 'gotchas', label: 'ephemeral' },
+    // ── NEW PATTERNS: Exercising research-sourced additions ──────────────
+    // -- Temporal (new patterns) --
+    { title: 'Session Attempt', content: 'Just tried rebuilding with the new Gradle wrapper and the sync still fails on the CI runner', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['temporal'] },
+    { title: 'Session Scope', content: 'In this session we found that the image cache grows without bound when switching tabs rapidly', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['temporal'] },
+    { title: 'Current Reality', content: 'As things stand we have three different auth flows coexisting and it causes confusion for new developers', topic: 'architecture', label: 'ephemeral', expectedSignals: ['temporal'] },
+    { title: 'Blocked Work', content: 'The deployment pipeline is still pending approval from the security team before we can ship the new SDK version', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['temporal'] },
+    { title: 'Last Attempt', content: 'Last time we ran the full integration suite it took over 40 minutes because of the Espresso screenshot tests', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['temporal'] },
+    // -- Fixed-bug (new patterns) --
+    { title: 'Works Now', content: 'The WebSocket reconnection works now after we added the exponential backoff with jitter to the retry logic', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['fixed-bug'] },
+    { title: 'Issue Tracker', content: 'This fixes #4521, the login screen was showing a blank state when the auth token expired during a background sync', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['fixed-bug'] },
+    { title: 'Root Cause Found', content: 'Turns out it was a threading issue. The database was being accessed from the main thread after the Room migration', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['fixed-bug'] },
+    { title: 'Not A Bug', content: 'The slowdown we observed was a false alarm, it was the profiler overhead causing the jank not the actual rendering', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['fixed-bug'] },
+    { title: 'Post-Fix', content: 'After the fix the app cold start time dropped from 3.2s to 1.8s on low-end devices', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['fixed-bug'] },
+    // -- Task-language (new patterns) --
+    { title: 'WIP Feature', content: 'This is a WIP implementation of the new notification grouping logic, still missing the DND time window handling', topic: 'architecture', label: 'ephemeral', expectedSignals: ['task-language'] },
+    { title: 'Code Marker', content: 'FIXME the error handling here silently swallows network exceptions and returns an empty list to the UI layer', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['task-language'] },
+    { title: 'Incomplete Work', content: 'The search module has a partial implementation of the autocomplete feature, missing the debounce and caching layers', topic: 'architecture', label: 'ephemeral', expectedSignals: ['task-language'] },
+    { title: 'Known Gap', content: "The new analytics tracker doesn't support custom dimensions yet, only standard event properties", topic: 'gotchas', label: 'ephemeral', expectedSignals: ['task-language'] },
+    // -- Investigation (new patterns) --
+    { title: 'Repro Attempt', content: "We can't reproduce the crash on any of our test devices, it only shows up in the Crashlytics dashboard for Xiaomi phones", topic: 'gotchas', label: 'ephemeral', expectedSignals: ['investigation'] },
+    { title: 'Error Observation', content: 'Getting a SocketTimeoutException every few minutes on the staging environment when hitting the search endpoint', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['investigation'] },
+    { title: 'Debug Action', content: 'Added logging to the auth token refresh flow to understand why some users are getting logged out after a background sync', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['investigation'] },
+    { title: 'Confusion', content: "Not sure why the Compose recomposition counter shows 15 recompositions for a single click event on the listing card", topic: 'gotchas', label: 'ephemeral', expectedSignals: ['investigation'] },
+    // -- Uncertainty (new patterns) --
+    { title: 'Knowledge Limit', content: 'As far as I know the Room migration should handle the schema change automatically but there might be edge cases', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['uncertainty'] },
+    { title: 'Caveat', content: 'Take this with a grain of salt but the profiling data suggests the main thread is being blocked by the image decoder', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['uncertainty'] },
+    { title: 'Brainstorm', content: 'Just a thought but we could use WorkManager instead of a foreground service for the background sync to simplify the lifecycle handling', topic: 'architecture', label: 'ephemeral', expectedSignals: ['uncertainty'] },
+    { title: 'Disclaimer', content: 'Your mileage may vary but on my Pixel 8 the scroll performance improved significantly after enabling baseline profiles', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['uncertainty'] },
+    { title: 'Self-Doubt', content: 'I could be wrong but I believe the auth interceptor retries the request automatically after refreshing the token', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['uncertainty'] },
+    { title: 'Pending Decision', content: 'The caching strategy for the feed is TBD, we might go with aggressive disk caching or server-side push depending on cost analysis', topic: 'architecture', label: 'ephemeral', expectedSignals: ['uncertainty'] },
+    { title: 'Subject to Change', content: 'The API contract for the new listing endpoint is subject to change, the backend team is still iterating on the response schema', topic: 'architecture', label: 'ephemeral', expectedSignals: ['uncertainty'] },
+    { title: 'Works For Me', content: 'The dark mode toggle works for me on Android 14 but several testers report it crashes on Samsung One UI 6 devices', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['uncertainty'] },
+    // -- Self-correction (new signal) --
+    { title: 'Retraction', content: 'Actually wait, the previous analysis about the memory leak was wrong. The leak is in the bitmap pool, not the view cache', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['self-correction'] },
+    { title: 'Changed Mind', content: 'On second thought, using a shared ViewModel for the messaging tabs would create a tight coupling between the tabs. Better to use event channels.', topic: 'architecture', label: 'ephemeral', expectedSignals: ['self-correction'] },
+    { title: 'Correction', content: "Scratch that, the timeout issue isn't in the OkHttp client. It's the server closing idle connections after 30 seconds.", topic: 'gotchas', label: 'ephemeral', expectedSignals: ['self-correction'] },
+    { title: 'Mistake', content: 'I was wrong about the ProGuard rule. The keep annotation on the parent class does not cascade to nested sealed subclasses.', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['self-correction'] },
+    // -- Meeting reference (new signal) --
+    { title: 'Meeting Decision', content: 'As discussed in the meeting we are going to deprecate the REST search endpoint and move to GraphQL for all new queries', topic: 'architecture', label: 'ephemeral', expectedSignals: ['meeting-reference'] },
+    { title: 'Someone Said', content: 'John mentioned that the backend team plans to rate-limit the notification endpoint to 100 requests per minute per user', topic: 'architecture', label: 'ephemeral', expectedSignals: ['meeting-reference'] },
+    { title: 'Standup Update', content: 'In today\'s standup the infrastructure team confirmed they will roll out the new CDN configuration by end of week', topic: 'gotchas', label: 'ephemeral', expectedSignals: ['meeting-reference'] },
+    // ── ADVERSARIAL: Sneaky ephemeral (disguised as durable) ──────────────
+    // These ARE ephemeral but avoid the detector's trigger words.
+    // False negatives here reveal genuine detection gaps.
+    // Temporal state without temporal keywords
+    { title: 'API Response Variance', content: 'The API response format varies between environments — development returns nested JSON while staging returns flat. Consumers must handle both shapes until the backend standardizes.', topic: 'gotchas', label: 'ephemeral' },
+    // Status observation without "currently"/"right now"
+    { title: 'Recommendation Latency', content: 'Response times from the recommendations service are elevated above normal baselines, causing the feed to render with empty placeholders on slow connections.', topic: 'gotchas', label: 'ephemeral' },
+    // Version-pinned fact that will become stale
+    { title: 'Payment SDK Regression', content: 'The third-party payment SDK version 4.3.2 introduced a regression with European card formats. Downgrading to 4.3.1 restores correct behavior for SEPA transactions.', topic: 'gotchas', label: 'ephemeral' },
+    // Ops issue without any trigger words
+    { title: 'Credential Propagation', content: 'The staging database credentials rotated and the config has not been propagated to all services. Two of the five backend pods are returning 500 on database queries.', topic: 'gotchas', label: 'ephemeral' },
+    // Feature comparison — a snapshot, but useful as a reference until the migration completes
+    // Moved to DURABLE_CASES: performance comparisons are useful reference data for years
+    // Decision not yet made — pure status
+    { title: 'Caching Approach Evaluation', content: 'Three caching strategies are under evaluation: write-through with Room, read-aside with DataStore, and server-push with WebSockets. Each has different trade-offs for offline support.', topic: 'architecture', label: 'ephemeral' },
+    // Observation about specific test run
+    // Moved to DURABLE_CASES: resource constraints are valid gotcha knowledge for months
+    // Version-specific behavior presented as universal
+    { title: 'Gradle Plugin Compatibility', content: 'The Detekt Gradle plugin 1.23.4 is incompatible with AGP 8.3 beta. Lint checks pass but the formatting rules produce false positives on Compose lambda parameters.', topic: 'gotchas', label: 'ephemeral' },
+    // Temporary architectural state without "for now"
+    // Moved to DURABLE_CASES: dual implementations can persist for years in production
+    // Performance regression without investigation keywords
+    { title: 'Cold Start Regression', content: 'App cold start time increased from 1.8s to 3.1s after the feature flag SDK integration. The initialization sequence blocks the main thread while fetching flag evaluations from the server.', topic: 'gotchas', label: 'ephemeral' },
+    // Incomplete migration presented as architecture
+    // Moved to DURABLE_CASES: mixed DI patterns persist for years during migrations
+    // Team practice not yet codified
+    // Moved to DURABLE_CASES: organizational process constraints persist indefinitely
+    // Experiment results — will change
+    // Moved to DURABLE_CASES: SDK overhead vs optimization tradeoff is durable knowledge
+    // ── ADVERSARIAL: Edge cases from agent (ambiguous, labeled by agent) ──
+    // Ephemeral edge cases
+    { title: 'Async Migration Plan', content: 'Converting the callback-based API handlers to async/await is blocked on Node 14 support but expected to start next quarter. This would improve error handling consistency across the networking layer.', topic: 'architecture', label: 'ephemeral' },
+    { title: 'Dashboard Re-render Spike', content: 'Dashboard re-renders 3x per navigation despite memo wrapper. Likely due to context changes in the theme provider. Performance audit scheduled to determine root cause.', topic: 'modules/messaging', label: 'ephemeral' },
+    { title: 'S3 Credential Workaround', content: 'S3 credentials failing intermittently after IAM policy rotation. Applied emergency policy override. Monitoring for recurrence before reverting the workaround code.', topic: 'gotchas', label: 'ephemeral' },
+    { title: 'Build Time Regression', content: 'Build times jumped from 45s to 2m30s after webpack config change. Source-map generation appears to be the bottleneck. Evaluating whether to revert or optimize the config.', topic: 'conventions', label: 'ephemeral' },
+    { title: 'CSS Specificity Conflict', content: 'Design tokens in global styles (specificity 0-1-0) are being overridden by component styles (0-1-1) in the checkout flow. Cascade strategy revision is being planned.', topic: 'conventions', label: 'ephemeral' },
+    { title: 'GraphQL DataLoader Rollout', content: 'DataLoader is being added to resolvers but the implementation covers only 7 of 10 resolvers. The remaining three are in the payment and auth modules and require special handling.', topic: 'architecture', label: 'ephemeral' },
+    { title: 'Rate Limit Spikes', content: 'Experiencing intermittent 429 errors with the Slack integration API after increasing notification volume. Adjusted retry backoff from linear to exponential. Monitoring for stability.', topic: 'modules/messaging', label: 'ephemeral' },
+    { title: 'Type Assertion Bypass', content: 'Some auth token validation uses any type to skip strict null checks. Refactoring depends on a TypeScript upgrade from 4.9 to 5.x which has not been scheduled.', topic: 'modules/auth', label: 'ephemeral' },
+    { title: 'Email Batch Size Experiment', content: 'Batch sizes from 50 to 500 were tested for the notification sender. 250 achieves best throughput without hitting rate limits. Final configuration has not been deployed.', topic: 'modules/messaging', label: 'ephemeral' },
+    { title: 'WebSocket Timeout Debate', content: 'Production sees occasional 60-second hangs before timeout on WebSocket connections. The team is evaluating a 30-second timeout with exponential backoff vs the current approach.', topic: 'gotchas', label: 'ephemeral' },
+    // ── ADVERSARIAL: Domain-specific ephemeral (Android jargon) ───────────
+    { title: 'AGP 8.2 Build Plugin Break', content: 'The custom build plugin broke after the AGP 8.2 upgrade due to variant API changes. The compileSdkVersion logic in BaseModule.gradle requires refactoring to use the new component API.', topic: 'conventions', label: 'ephemeral' },
+    { title: 'Room v14 Migration Crash', content: 'The v14 database migration has constraint violations on the User table unique index. The schema change needs an intermediate migration step to preserve existing data integrity.', topic: 'modules/messaging', label: 'ephemeral' },
+    { title: 'ProfileScreen Recomposition', content: 'ProfileScreen recomposes on every navigation back due to a mutableStateOf in the ViewModel that needs conversion to StateFlow across the MVI pipeline.', topic: 'architecture', label: 'ephemeral' },
+    { title: 'Retrofit Timeout on Slow Networks', content: 'API calls timing out on slow networks due to the 30s default OkHttp timeout in RetrofitFactory. Network logs needed to determine if the server or the client is the bottleneck.', topic: 'modules/network', label: 'ephemeral' },
+    { title: 'Espresso Flake on CI', content: 'The inventory test suite is flaky on CI. The race condition is in the TestScheduler, not the IdlingResource setup as initially suspected.', topic: 'gotchas', label: 'ephemeral' },
+    { title: 'WorkManager Constraint Bug', content: 'The daily sync job fails to trigger because BatteryLevelConstraint was not properly backported to the generic WorkRequest builder in SyncWorker.kt.', topic: 'gotchas', label: 'ephemeral' },
+    { title: 'DataStore Migration Incomplete', content: 'SearchPreferences migration from SharedPreferences to DataStore is underway. The Proto schema compiles but the backwards-compatibility wrapper is not finished.', topic: 'modules/messaging', label: 'ephemeral' },
+    { title: 'Deep Link Back Stack Collision', content: 'The deep link handler pushes duplicate destinations on the back stack during cold start. NavBackStackEntry IDs collide in our custom NavController extension.', topic: 'modules/messaging', label: 'ephemeral' },
+    // ── Agent-generated: Python/Django engineer (15 ephemeral) ──────────────
+    { title: 'PostgreSQL Connection Pool Saturation', content: 'The database connection pool is hitting 95% utilization during peak hours between 2-4pm. We\'ve configured max_connections=100 in pgbouncer, but concurrent Celery workers are consuming more connections than anticipated.', topic: 'modules/database', label: 'ephemeral' },
+    { title: 'Celery Task Retry Logic', content: 'Background job failures on payment processing endpoints are being caused by a race condition where the merchant account hasn\'t finished provisioning when the task retries. Adding a 5-second exponential backoff resolved most occurrences this week.', topic: 'modules/celery', label: 'ephemeral' },
+    { title: 'FastAPI Request Validation Issue', content: 'The endpoint for bulk user imports is failing validation when CSV files contain UTF-8 BOM headers. A preprocessing step strips the BOM before validation reaches Pydantic.', topic: 'modules/api', label: 'ephemeral' },
+    { title: 'Mypy Type Checking Configuration', content: 'The codebase is currently at 78% type coverage. Legacy authentication modules are excluded from mypy checks. We\'re incrementally migrating old modules by adding ignore comments and gradually removing them.', topic: 'conventions', label: 'ephemeral' },
+    { title: 'Docker Build Cache Issue', content: 'Running pip install -r requirements.txt in the Dockerfile layer is rebuilding all packages every time source code changes. We restructured the layer ordering to install dependencies first, reducing build times from 8 minutes to 2 minutes.', topic: 'architecture', label: 'ephemeral' },
+    { title: 'Gunicorn Worker Class Selection', content: 'We\'re running gevent workers with 50 greenlets per worker, but CPU-bound analytics queries are blocking the event loop. Switching to sync workers for the analytics API endpoint resulted in better throughput.', topic: 'architecture', label: 'ephemeral' },
+    { title: 'SQLAlchemy Session Scope Issue', content: 'The FastAPI application is using scoped sessions incorrectly, causing connections to remain open after request completion. We patched the dependency injection to explicitly close sessions, but memory usage should be monitored.', topic: 'modules/database', label: 'ephemeral' },
+    { title: 'DRF Throttling Rate Limit Tuning', content: 'User throttling is currently set to 100 requests per minute globally, but machine learning API endpoints are hitting the limit during batch inference jobs. We\'re implementing a separate throttle class.', topic: 'modules/api', label: 'ephemeral' },
+    { title: 'uv Package Manager Switch', content: 'Installing dependencies with uv is roughly 10x faster than pip. We switched from pip to uv in CI/CD pipelines last month, cutting deployment times significantly.', topic: 'preferences', label: 'ephemeral' },
+    { title: 'Redis Key Naming Conflict', content: 'A naming collision occurred between cache keys and session keys in Redis, causing sessions to be evicted when the cache reached capacity. We implemented a namespace prefix strategy to separate the keyspaces.', topic: 'modules/database', label: 'ephemeral' },
+    { title: 'Alembic Auto-generation Limitations', content: 'Running alembic revision --autogenerate sometimes misses custom SQL operations. We caught a missing NOT NULL constraint this week that would have caused production issues.', topic: 'modules/database', label: 'ephemeral' },
+    { title: 'Pytest Fixture Scope Misconfiguration', content: 'Database fixtures are currently module-scoped, which means database state persists between test modules. We\'re refactoring to function-scoped fixtures to ensure test isolation.', topic: 'preferences', label: 'ephemeral' },
+    { title: 'Celery Beat Scheduler Drift', content: 'The Celery Beat scheduler is drifting by approximately 30 seconds per day due to task execution times compounding. We implemented a more precise scheduler library, though the deployment is still being tested in staging.', topic: 'modules/celery', label: 'ephemeral' },
+    { title: 'Docker Layer Build Context Size', content: 'The buildx command is taking 45 seconds just to prepare the context before building. We need to add more entries to .dockerignore to exclude node_modules, test files, and other unnecessary artifacts.', topic: 'architecture', label: 'ephemeral' },
+    { title: 'FastAPI Dependency Caching', content: 'A recent addition of use_cache=True to FastAPI dependencies is causing authentication state to persist between requests in test mode. Disabling the cache resolved test failures, but we need to determine if this impacts production.', topic: 'modules/auth', label: 'ephemeral' },
+    // ── Agent-generated: React/TypeScript engineer (15 ephemeral) ───────────
+    { title: 'Dashboard Performance Regression', content: 'The chart rendering on the analytics dashboard is experiencing 200ms+ delays when loading 50k data points. We\'ve isolated it to inefficient re-renders in the TanStack Query cache invalidation.', topic: 'modules/api', label: 'ephemeral' },
+    { title: 'Node 18 Build Workaround', content: 'The Vite build fails with ES module resolution errors in our CI pipeline. We\'ve pinned Node to 16.19.1 as a temporary measure. Once we upgrade ESLint to 9.x, this should be resolved.', topic: 'conventions', label: 'ephemeral' },
+    { title: 'OAuth Flow Timeout', content: 'Playwright tests for the OAuth redirect flow are timing out intermittently in parallel test runs. We suspect it\'s related to how Vitest manages mocked window.location changes.', topic: 'modules/auth', label: 'ephemeral' },
+    { title: 'Zustand State Slice Migration', content: 'We\'re in the process of refactoring the notification store to use Zustand slices instead of a monolithic store structure. The preliminary implementation shows promise, though we\'re still testing edge cases.', topic: 'modules/state', label: 'ephemeral' },
+    { title: 'Radix UI Dialog Z-Index', content: 'The Radix UI Dialog overlay is rendering with incorrect z-index values when nested inside portaled Popover components. We\'ve added a workaround using Tailwind\'s arbitrary values.', topic: 'modules/ui', label: 'ephemeral' },
+    { title: 'React Hook Form Double Validation', content: 'Our custom Zod schema validation is running twice on form submission in development mode. We traced it to StrictMode wrapping, and we\'re still deciding whether to add a debounce.', topic: 'modules/state', label: 'ephemeral' },
+    { title: 'Prettier Tailwind Class Sorting', content: 'Prettier\'s class sorting is occasionally reordering Tailwind utility classes unpredictably when combined with our custom Prettier plugin. We\'ve adjusted the plugin configuration.', topic: 'conventions', label: 'ephemeral' },
+    { title: 'Next.js Image in Staging', content: 'The Next.js Image component is serving unoptimized images in our staging environment due to a misconfiguration of the unoptimized flag in next.config.js.', topic: 'modules/ui', label: 'ephemeral' },
+    { title: 'TypeScript Generic Inference', content: 'Generic type parameters in our TanStack Query hooks aren\'t inferring correctly when passed through Zustand selectors. We\'re exploring whether to add explicit type assertions.', topic: 'modules/api', label: 'ephemeral' },
+    { title: 'Storybook Build Performance', content: 'Storybook startup time has increased to 45 seconds after adding 12 new component stories. Initial testing shows excluding node_modules/.cache might improve build speed.', topic: 'conventions', label: 'ephemeral' },
+    { title: 'Auth Token Refresh Race', content: 'Multiple simultaneous API requests are triggering token refresh multiple times during the same second. We\'ve added a pending state flag to queue refresh attempts, but haven\'t fully validated the fix.', topic: 'modules/auth', label: 'ephemeral' },
+    { title: 'Tailwind IntelliSense Issue', content: 'The custom color palette we built for brand consistency is not being recognized by Tailwind IntelliSense in VS Code. We\'re still troubleshooting whether it\'s a path configuration issue.', topic: 'conventions', label: 'ephemeral' },
+    { title: 'TanStack Query Cache Experiment', content: 'We\'re experimenting with TanStack Query\'s predicate-based cache invalidation. Early testing suggests this approach reduces unnecessary re-renders, but we need to validate with larger datasets.', topic: 'modules/api', label: 'ephemeral' },
+    { title: 'Radix UI Bundle Size', content: 'A recent audit shows our Radix UI imports are contributing 18kb to the initial bundle despite tree-shaking. We\'re evaluating whether switching to individual component imports would improve page load.', topic: 'modules/ui', label: 'ephemeral' },
+    { title: 'Accessibility Test Coverage Gap', content: 'Playwright accessibility checks are only covering 60% of our interactive components. We\'re expanding test coverage, though the implementation approach is still being decided.', topic: 'conventions', label: 'ephemeral' },
+    // ── Agent-generated: DevOps/infra engineer (15 ephemeral) ───────────────
+    { title: 'EKS API Latency Spike', content: 'The Kubernetes API server is experiencing elevated response times (200-300ms p99) on the production cluster. This appears to be correlated with etcd leader election during node pool expansion.', topic: 'modules/kubernetes', label: 'ephemeral' },
+    { title: 'RDS Instance Type Migration', content: 'We\'re transitioning the main database from db.r5.2xlarge to db.r6i.2xlarge. The primary instance has been migrated and we\'re monitoring replication lag during the standby conversion.', topic: 'architecture', label: 'ephemeral' },
+    { title: 'GitHub Actions Runner Disk Space', content: 'Our self-hosted GitHub Actions runners are accumulating Docker layer cache, consuming 80% of the 100GB ephemeral storage per pod. We\'ve implemented a nightly cleanup job.', topic: 'modules/ci', label: 'ephemeral' },
+    { title: 'Terraform State Lock Contention', content: 'The infrastructure CI pipeline had multiple concurrent terraform apply operations against staging, causing state lock conflicts. We\'ve implemented a mutex in our GitHub Actions workflow.', topic: 'modules/ci', label: 'ephemeral' },
+    { title: 'ArgoCD Sync Wave Bug', content: 'A recent ArgoCD upgrade to 2.8.0 introduced a regression where sync waves with identical priority weren\'t respecting manifest order. We\'ve pinned back to 2.7.5.', topic: 'modules/ci', label: 'ephemeral' },
+    { title: 'Prometheus Buffer Backup', content: 'The Prometheus instance pushing metrics to Thanos is hitting the WAL buffer limit due to a network outage. We\'ve increased the queue capacity temporarily.', topic: 'modules/monitoring', label: 'ephemeral' },
+    { title: 'Nginx Certificate Renewal Failure', content: 'The cert-manager hook failed to renew the TLS certificate for api.example.com due to DNS propagation delays. We manually triggered a renewal and verified the new certificate is active.', topic: 'modules/networking', label: 'ephemeral' },
+    { title: 'Istio Sidecar Rate Limiting', content: 'Istio\'s sidecar injector reached the API server rate limit while attempting to inject into 150 new pods simultaneously during a cluster autoscaling event.', topic: 'modules/kubernetes', label: 'ephemeral' },
+    { title: 'Datadog Agent Memory Leak', content: 'The Datadog agent DaemonSet pods are consuming increasing memory over 5-7 days of uptime, suggesting a memory leak in version 7.45.0. We\'ve upgraded to 7.46.0 in the canary namespace.', topic: 'modules/monitoring', label: 'ephemeral' },
+    { title: 'Lambda Timeout During Migration', content: 'Our data export Lambda function is timing out at 15 minutes when processing the larger production dataset. We\'ve increased the timeout to 20 minutes as a temporary measure.', topic: 'architecture', label: 'ephemeral' },
+    { title: 'Vault Token Expiry in CI', content: 'The GitHub Actions runner\'s Vault token is expiring mid-pipeline when jobs run for longer than the 1-hour TTL. We\'ve increased the TTL to 4 hours.', topic: 'gotchas', label: 'ephemeral' },
+    { title: 'ECR Image Scanning CVE', content: 'A critical CVE was discovered in the base Node.js image we\'re using in production. We\'ve rebuilt and pushed a patched version and are coordinating a rapid rollout.', topic: 'gotchas', label: 'ephemeral' },
+    { title: 'Helm Chart Dependency Mismatch', content: 'After upgrading to Helm chart version 3.2.0, bundled dependency versions no longer match the cluster. We\'ve locked the chart version at 3.1.5 until we validate compatibility.', topic: 'modules/ci', label: 'ephemeral' },
+    { title: 'Cloud NAT IP Exhaustion', content: 'The Cloud NAT gateway is running low on public IP allocations and we\'re observing packet drops on outbound connections. We\'ve added an additional public IP.', topic: 'modules/networking', label: 'ephemeral' },
+    { title: 'Ansible EBS Volume Idempotency', content: 'Running the infrastructure playbook twice created duplicate EBS volumes because the attachment task wasn\'t properly idempotent. We\'ve refactored to check existing attachments.', topic: 'preferences', label: 'ephemeral' },
+    // ── Agent-generated: iOS/Swift engineer (15 ephemeral) ──────────────────
+    { title: 'SwiftUI State Restoration Leak', content: 'There\'s a memory leak in the navigation state restoration on iOS 17.2 where @StateObject retains the previous view controller. Our workaround is to manually clear the navigationPath in onDisappear.', topic: 'modules/ui', label: 'ephemeral' },
+    { title: 'Kingfisher Cache Warming', content: 'We\'re preloading user avatars from the API response into Kingfisher\'s cache before navigating to the home feed. This reduced perceived load time by 200ms on slower devices.', topic: 'modules/networking', label: 'ephemeral' },
+    { title: 'Xcode Preview Crashes', content: 'The live preview canvas crashes when using ObservableObject with certain Combine publishers in the current Xcode version. Workaround is to use @StateObject. This appears to be fixed in the beta.', topic: 'conventions', label: 'ephemeral' },
+    { title: 'SPM Package Resolution', content: 'The Alamofire version constraint in Package.resolved is causing build failures in CI when using Xcode Cloud. We pinned it to 5.8.1 as a temporary fix.', topic: 'modules/networking', label: 'ephemeral' },
+    { title: 'Coordinator Navigation Debugging', content: 'Added logging to track navigation stack depth in the AppCoordinator. Found that deep linking sometimes causes duplicate coordinator instances. Need to verify this doesn\'t impact performance.', topic: 'modules/navigation', label: 'ephemeral' },
+    { title: 'TCA Environment Migration', content: 'We\'re moving all API clients from direct initialization to environment-injected dependencies in the TCA store. This refactor is halfway complete in the authentication module.', topic: 'architecture', label: 'ephemeral' },
+    { title: 'Combine Pipeline Memory Pressure', content: 'Our event publishing pipeline in the analytics service is holding references longer than expected when there are 3+ concurrent subscriptions. Considering switching to AsyncStream.', topic: 'modules/networking', label: 'ephemeral' },
+    { title: 'Feed Frame Drops', content: 'The feed view drops frames when scrolling fast on iPhone 11 devices. Profiling shows high CPU usage in the image rendering pipeline. Testing a change to defer image decoding.', topic: 'gotchas', label: 'ephemeral' },
+    { title: 'Codable Decoding Strategy Mismatch', content: 'The API backend changed to snake_case JSON keys this week, but our Codable models use camelCase. Updated the JSONDecoder.keyDecodingStrategy as a quick fix while the API client is being refactored.', topic: 'modules/networking', label: 'ephemeral' },
+    { title: 'Xcode 16 Build Config', content: 'The new build system in Xcode 16 requires explicit bridging header configuration for mixed ObjC/Swift targets. One legacy framework still has configuration issues.', topic: 'preferences', label: 'ephemeral' },
+    { title: 'OAuth Token Refresh Race', content: 'There\'s a race condition in the token refresh logic when multiple requests attempt to refresh simultaneously. Evaluating NSLock versus a Swift Concurrency actor.', topic: 'modules/networking', label: 'ephemeral' },
+    { title: 'SwiftUI Binding Observation', content: 'We\'re updating how we handle derived state bindings to prevent unnecessary view recalculations. Using @Published with custom get/set instead of direct @State mutations.', topic: 'architecture', label: 'ephemeral' },
+    { title: 'CocoaPods Dependency Hell', content: 'The Pods lock file had conflicting version constraints. Pinned GoogleUtilities to 7.11.5 as a temporary measure pending resolution of transitive dependency conflicts.', topic: 'modules/networking', label: 'ephemeral' },
+    { title: 'WebView Bridge Timing', content: 'The WKWebView JavaScript bridge sometimes drops messages when the view loads asynchronously. Wrapping the bridge setup in a callback resolved most cases, but occasional messages still get lost on slower devices.', topic: 'gotchas', label: 'ephemeral' },
+    { title: 'Navigation Stack Memory', content: 'Added a test helper to verify that popped views release their ViewModels correctly. Noticed that some complex hierarchies still hold references longer than expected.', topic: 'modules/navigation', label: 'ephemeral' },
+    // ── Agent-generated: Data engineer (15 ephemeral) ───────────────────────
+    { title: 'Kafka Broker Disk Pressure', content: 'The partition rebalancing on brokers 3-5 caused sustained disk I/O above 85% for approximately 36 hours. We throttled producer throughput to 60% and adjusted log retention to 7 days.', topic: 'modules/streaming', label: 'ephemeral' },
+    { title: 'Spark Job Memory Overhead', content: 'Recent Parquet files from the customer analytics ETL are using 1.3x the expected heap space during deserialization. Switched to Arrow-backed in-memory format for intermediate stages.', topic: 'modules/etl', label: 'ephemeral' },
+    { title: 'BigQuery Slot Reservation', content: 'Upgraded from flex slots to annual commitment (500 slots) due to inconsistent query latencies during peak hours. The migration was initiated last Monday and should complete by week-end.', topic: 'modules/warehouse', label: 'ephemeral' },
+    { title: 'dbt Surrogate Key Collision', content: 'A hash collision was detected in the customer_master model where two distinct upstream records generated the same SHA-256 surrogate key. The affected records have been reprocessed.', topic: 'modules/etl', label: 'ephemeral' },
+    { title: 'Snowflake Clone for Schema Testing', content: 'Created zero-copy clones of prod_orders and prod_payments tables to validate the new nullable column addition. Clone storage is temporary and will be dropped after certification.', topic: 'modules/warehouse', label: 'ephemeral' },
+    // Moved to DURABLE_CASES: encoding choice with measured improvement
+    // Moved to DURABLE_CASES: stable configuration after tuning
+    { title: 'Airflow DAG Backfill', content: 'The warehouse_staging.users_iceberg table had misaligned partition boundaries due to a schema evolution bug. Backfilled April 1-15 data by manually triggering the ingestion DAG.', topic: 'modules/warehouse', label: 'ephemeral' },
+    // Moved to DURABLE_CASES: optimization decision with measured result
+    { title: 'Polars Lazy Evaluation Issue', content: 'Migrated data quality checks to Polars, but the LazyFrame evaluation model caused assertions to pass when they should have failed. Updated all validation logic to call .collect() before running expectations.', topic: 'modules/quality', label: 'ephemeral' },
+    { title: 'Prefect Flow Timeout', content: 'The conform_dimensions flow was timing out at 45 minutes when backfilling 3 years of historical customer data. Implemented checkpoint-based recovery and split the workload into weekly batches.', topic: 'modules/etl', label: 'ephemeral' },
+    { title: 'Dagster Stale Dependencies', content: 'Discovered that 6 downstream assets were waiting on a deprecated intermediate asset that was removed but still declared as a dependency. Removed the stale dependency definitions.', topic: 'modules/etl', label: 'ephemeral' },
+    { title: 'Flink Operator State Migration', content: 'Upgraded Flink from 1.14 to 1.16, but the session window state was serialized with the old Kryo format. Savepoint restore failed until we reverted the TypeInformation registration.', topic: 'modules/streaming', label: 'ephemeral' },
+    { title: 'Kafka Schema Registry Breaking Change', content: 'A producer upgraded its Avro schema to add 3 new required fields without default values, which broke all existing consumers. Schema registry compatibility checks were set to BACKWARD only instead of FORWARD_TRANSITIVE.', topic: 'modules/streaming', label: 'ephemeral' },
+    { title: 'Spark Shuffle Spill', content: 'A broadcast join consumed 12GB of driver memory attempting to serialize the 8GB lookup table, causing spill to disk and GC pauses. Re-partitioned the broadcast table to 32 chunks.', topic: 'modules/etl', label: 'ephemeral' },
+    // ── Agent-generated: Rust systems engineer (15 ephemeral) ───────────────
+    { title: 'Tokio Panic Propagation', content: 'We found that spawning tasks with tokio::spawn before the runtime enters full_futures mode causes unexpected panic propagation in edge cases. We\'ve patched our task spawning to buffer tasks until runtime initialization completes.', topic: 'modules/runtime', label: 'ephemeral' },
+    { title: 'Serde JSON Stack Overflow', content: 'Deserialization of deeply nested JSON structures with serde_json 1.0.107 hits stack limits before the depth limit check fires. The issue resolves with a targeted serde version bump.', topic: 'modules/parser', label: 'ephemeral' },
+    { title: 'Rayon Thread Pool Contention', content: 'Our parallel processing pipeline experiences significant contention when rayon pool size exceeds NUMA boundaries on our test hardware. We\'ve tuned the work-stealing thresholds.', topic: 'modules/runtime', label: 'ephemeral' },
+    { title: 'Arc Mutex Lock Timeout', content: 'We observed deadlock-like behavior when Arc<Mutex<T>> holders panic between lock acquisition and release in the state machine layer. Added guard re-entrancy checks for the v2 refactor.', topic: 'conventions', label: 'ephemeral' },
+    { title: 'Clippy Missing Docs False Positives', content: 'Clippy 0.1.73 flags internal macro-generated trait methods even when doc comments exist on the macro invocation. Suppressing via allow attributes. This may change in later clippy releases.', topic: 'preferences', label: 'ephemeral' },
+    { title: 'Miri False Positive', content: 'Running certain unit tests through miri reports a data race on Arc<AtomicUsize> even with proper Acquire/Release semantics. Using cfg miri to skip those specific assertions pending an miri update.', topic: 'gotchas', label: 'ephemeral' },
+    { title: 'Crossbeam Channel Regression', content: 'Crossbeam 0.8.x shows degraded throughput compared to 0.7.x for high-frequency message sends. We\'re keeping 0.7.4 pinned in Cargo.lock while evaluating alternatives.', topic: 'modules/networking', label: 'ephemeral' },
+    { title: 'Pin Projection Issue', content: 'Our attempt to use pin-project for the cache coherency layer revealed that field visibility rules interact badly with macro hygiene. We\'ve moved to manual projection with explicit safety comments.', topic: 'gotchas', label: 'ephemeral' },
+    { title: 'FFI Segfault with CStr Lifetimes', content: 'The wrapping layer for our C dependency wasn\'t properly validating pointer lifetimes across the boundary. AddressSanitizer caught use-after-free in the conversion helper. Refactored the CStr ownership model.', topic: 'modules/networking', label: 'ephemeral' },
+    { title: 'Procedural Macro Span Loss', content: 'Our derive macro loses column information when expanding nested attributes, making error messages from proc_macro2 unhelpful. We\'re working around this by injecting synthetic spans.', topic: 'conventions', label: 'ephemeral' },
+    { title: 'No_std Allocator Race', content: 'The no_std build path had a subtle race in global_allocator setup between const initialization and runtime thread spawning. Added explicit synchronization barriers during startup.', topic: 'modules/runtime', label: 'ephemeral' },
+    { title: 'Unsafe Block Audit', content: 'We identified three unsafe blocks in the serialization fast-path that incorrectly assumed alignment properties after recent refactoring. All three are marked for removal in the next API version.', topic: 'gotchas', label: 'ephemeral' },
+    { title: 'Trait Object Vtable Explosion', content: 'Trait objects derived from our generic Effect trait were generating 18KB vtables due to monomorphization. Splitting into two traits reduced this significantly.', topic: 'architecture', label: 'ephemeral' },
+    { title: 'Cargo Feature Interaction Bug', content: 'Enabling both experimental-simd and avx2-optimization features creates a link error in dependencies. Documented as a known issue; users must pick one.', topic: 'preferences', label: 'ephemeral' },
+    { title: 'Lifetime Inference in Closures', content: 'Generic closures capturing references in our callback API required explicit lifetime annotations that shouldn\'t be necessary. Workaround: boxing closures into dyn Fn. Revisiting once HRTB becomes more stable.', topic: 'gotchas', label: 'ephemeral' },
+];
+// ─── DURABLE CASES (should produce NO signals) ───────────────────────────
+const DURABLE_CASES = [
+    // -- Architecture patterns (12 cases) --
+    { title: 'MVI Architecture', content: 'The messaging feature uses MVI with standalone reducer classes. Events are modeled as sealed interfaces for exhaustive handling. ViewModels act as orchestrators and never contain business logic.', topic: 'architecture', label: 'durable' },
+    { title: 'Module Structure', content: 'Each feature module follows a three-layer structure: api (public interfaces), impl (implementation with @ContributesBinding), and test (fakes and fixtures).', topic: 'architecture', label: 'durable' },
+    { title: 'State Management', content: 'UI state is always modeled as an immutable data class. State transitions happen exclusively through the reducer. ViewModels expose StateFlow and never MutableStateFlow.', topic: 'architecture', label: 'durable' },
+    { title: 'Navigation Pattern', content: 'Navigation events flow from the ViewModel through a SharedFlow. The Activity or Fragment observes and delegates to the NavController. Deep links are handled at the Activity level.', topic: 'architecture', label: 'durable' },
+    { title: 'Error Handling', content: 'All network calls return Result<T> instead of throwing exceptions. Use suspendRunCatching for suspend functions. Map errors to sealed error types at the repository boundary.', topic: 'architecture', label: 'durable' },
+    { title: 'Coroutine Scoping', content: 'ViewModels use viewModelScope for all coroutine launching. Use cases are suspend functions that do not manage their own scope. Background work uses a supervised scope injected via DI.', topic: 'architecture', label: 'durable' },
+    { title: 'Data Flow', content: 'The data layer exposes Flow-based APIs. Room DAOs return Flow<List<T>>. Network responses are mapped to domain models at the repository layer before being exposed upstream.', topic: 'architecture', label: 'durable' },
+    { title: 'Compose Architecture', content: 'Compose screens follow a three-tier hierarchy: Screen (connects to ViewModel), Content (stateless, receives state and events), Components (reusable UI primitives).', topic: 'architecture', label: 'durable' },
+    { title: 'Testing Architecture', content: 'Each module has a dedicated test module with fakes for all public interfaces. Use SampleProviders for generating test data. Turbine for Flow testing, ComposeTestRule for UI testing.', topic: 'architecture', label: 'durable' },
+    { title: 'DI Architecture', content: 'Dependency injection uses Anvil with @ContributesBinding(AppScope::class) for all production bindings. Constructor injection only, no field injection. Each feature has its own component scope.', topic: 'architecture', label: 'durable' },
+    { title: 'Cache Strategy', content: 'Network responses are cached in Room with a TTL of 5 minutes for listing data and 24 hours for static content. Cache invalidation happens on user-triggered refresh or app resume.', topic: 'architecture', label: 'durable' },
+    { title: 'Event Bus', content: 'Cross-feature communication uses typed event channels scoped to AppScope. Events are sealed interfaces. Each feature declares its own event types in its api module.', topic: 'architecture', label: 'durable' },
+    // -- Coding conventions (12 cases) --
+    { title: 'Naming Convention', content: 'Use the Real prefix instead of Impl for implementation classes. Example: RealMessagingRepository implements MessagingRepository. This convention applies across all modules.', topic: 'conventions', label: 'durable' },
+    { title: 'Sealed Interfaces', content: 'Prefer sealed interfaces over sealed classes for all event and state hierarchies. Sealed interfaces allow implementing multiple hierarchies and are more extensible.', topic: 'conventions', label: 'durable' },
+    { title: 'Immutability Rule', content: 'All UI state classes must be immutable data classes. Avoid MutableStateFlow in ViewModels. Use the scan operator with a reducer to produce the state flow.', topic: 'conventions', label: 'durable' },
+    { title: 'Null Safety', content: 'Never use the !! operator in production code. Handle nullability explicitly with safe calls, elvis operator, or early returns. Use @NonNull annotations at Java interop boundaries.', topic: 'conventions', label: 'durable' },
+    { title: 'Test Naming', content: 'Test methods use backtick syntax with descriptive names. Format: `given X when Y then Z`. Example: `given expired token when refreshing then returns new token`.', topic: 'conventions', label: 'durable' },
+    { title: 'Error Types', content: 'Use sealed interfaces for error types at feature boundaries. Each feature defines its own error hierarchy. Map platform exceptions to domain errors at the repository layer.', topic: 'conventions', label: 'durable' },
+    { title: 'Compose Previews', content: 'Every public Composable function must have a corresponding @Preview function. Use SampleProviders for preview data. Include both light and dark theme previews.', topic: 'conventions', label: 'durable' },
+    { title: 'Value Classes', content: 'Use value classes (inline classes) for type-safe primitives. Example: value class UserId(val value: String). This prevents mixing up ID types at compile time.', topic: 'conventions', label: 'durable' },
+    { title: 'Extension Functions', content: 'Use extension functions to add behavior to types without modifying them. Place extensions in a file named after the extended type. Keep extensions pure and side-effect free.', topic: 'conventions', label: 'durable' },
+    { title: 'Coroutine Convention', content: 'Use Dispatchers.IO for network and disk operations. Never hardcode dispatchers; inject them through constructor parameters. Use TestDispatcher in unit tests.', topic: 'conventions', label: 'durable' },
+    { title: 'Git Branching', content: 'Branch names follow the pattern: feature/username/ticket-number_short-description. Example: feature/etienneb/acei-1234_messaging-reducer. Always branch from main.', topic: 'conventions', label: 'durable' },
+    { title: 'Code Review', content: 'All PRs require at least one approval. Auto-assign reviewers based on CODEOWNERS. Run detekt and lint locally before pushing. Snapshot tests must be verified with verifyPaparazzi.', topic: 'conventions', label: 'durable' },
+    // -- Active gotchas (still relevant) (12 cases) --
+    { title: 'Build Cache', content: 'Must run clean build after modifying Tuist-generated files. Incremental builds pick up stale generated sources and produce cryptic compile errors.', topic: 'gotchas', label: 'durable' },
+    { title: 'ProGuard Rules', content: 'Kotlin serialization requires explicit ProGuard keep rules for each serializable class. The compiler plugin does not generate these automatically.', topic: 'gotchas', label: 'durable' },
+    { title: 'Compose Stability', content: 'List parameters in Composables are unstable by default. Use kotlinx.collections.immutable ImmutableList to avoid unnecessary recompositions.', topic: 'gotchas', label: 'durable' },
+    { title: 'Room Migration', content: 'Room schema migrations must be written manually for any column addition or type change. AutoMigration only handles simple cases like table creation.', topic: 'gotchas', label: 'durable' },
+    { title: 'Coroutine Leak', content: 'Using GlobalScope for background work causes memory leaks. All coroutine work must be tied to a lifecycle-aware scope like viewModelScope or a supervised custom scope.', topic: 'gotchas', label: 'durable' },
+    { title: 'Anvil Limitation', content: 'Anvil cannot generate bindings for generic interfaces. When a use case implements FlowUseCase<Input, Output>, you must create a manual @Binds module.', topic: 'gotchas', label: 'durable' },
+    { title: 'Android 14 Photo Picker', content: 'On Android 14 and above, the photo picker API requires READ_MEDIA_VISUAL_USER_SELECTED permission. The old READ_EXTERNAL_STORAGE permission is no longer sufficient.', topic: 'gotchas', label: 'durable' },
+    { title: 'Compose Navigation', content: 'Compose Navigation loses state on configuration change when using rememberSaveable with custom Saver. Must implement parcelize on the state class.', topic: 'gotchas', label: 'durable' },
+    { title: 'Flaky Test Pattern', content: 'Tests that launch coroutines with delay must use advanceUntilIdle or advanceTimeBy with TestDispatcher. Using runBlocking will cause the test to hang or flake.', topic: 'gotchas', label: 'durable' },
+    { title: 'Hilt Limitation', content: 'Hilt does not support injection into abstract classes. Use @Inject constructor on concrete implementations and @ContributesBinding on the interface.', topic: 'gotchas', label: 'durable' },
+    { title: 'Bitmap Memory', content: 'Loading full-resolution images into ImageView without downsampling causes OOM on low-memory devices. Always use Coil with size constraints matching the view dimensions.', topic: 'gotchas', label: 'durable' },
+    { title: 'WebSocket Reconnection', content: 'The OkHttp WebSocket does not automatically reconnect on network change. The messaging module implements a custom reconnection strategy using ConnectivityManager callbacks.', topic: 'gotchas', label: 'durable' },
+    // -- User identity and preferences (8 cases) --
+    { title: 'Identity', content: 'Etienne, Senior Android Engineer at Zillow. Primary focus on messaging feature porting from iOS to Android.', topic: 'user', label: 'durable' },
+    { title: 'Code Style', content: 'Prefer sealed interfaces over sealed classes. Always use immutable data classes for state. Avoid MutableStateFlow. Use functional programming patterns.', topic: 'preferences', label: 'durable' },
+    { title: 'Testing Preference', content: 'Prefer fakes over mocks for unit testing. Use Turbine for Flow testing. Write descriptive test names in backtick syntax.', topic: 'preferences', label: 'durable' },
+    { title: 'Architecture Preference', content: 'Use MVI pattern for all features. Reducers must be pure functions. ViewModels are orchestrators only. Derive all side effects from state.', topic: 'preferences', label: 'durable' },
+    { title: 'Error Handling Pref', content: 'Use Result<T> for error handling instead of exceptions. Use runCatching and suspendRunCatching. Map errors at boundaries.', topic: 'preferences', label: 'durable' },
+    { title: 'DI Preference', content: 'Use Anvil with constructor injection for all bindings. No field injection. Use @ContributesBinding for production and @Binds for generic interfaces.', topic: 'preferences', label: 'durable' },
+    { title: 'Communication Style', content: 'Be concise and technical. No emojis in MR descriptions. Prove points with evidence. Prefer declarative APIs over imperative ones.', topic: 'preferences', label: 'durable' },
+    { title: 'Documentation Preference', content: 'Document why, not what. Assume the reader knows the language. Use self-documenting code with explicit types over comments.', topic: 'preferences', label: 'durable' },
+    // -- Module knowledge (8 cases) --
+    { title: 'Messaging Module', content: 'The messaging module is at features/messaging/ with api, impl, and test submodules. The reducer handles all state transitions for conversation list and message thread views.', topic: 'modules/messaging', label: 'durable' },
+    { title: 'Auth Module', content: 'Authentication is handled by a shared auth module. Token refresh is automatic via an OkHttp interceptor. The auth state is exposed as a StateFlow from AuthManager.', topic: 'modules/auth', label: 'durable' },
+    { title: 'Analytics Module', content: 'Analytics events are defined as sealed interfaces per feature. The analytics module provides a global AnalyticsTracker interface. Each feature contributes its tracker via Anvil.', topic: 'modules/analytics', label: 'durable' },
+    { title: 'Network Module', content: 'The network module provides a configured OkHttpClient and Retrofit instance. All API interfaces are defined in feature api modules and bound to the shared Retrofit.', topic: 'modules/network', label: 'durable' },
+    { title: 'Image Loading', content: 'Image loading uses Coil with a shared ImageLoader configured with disk cache and memory cache. Custom fetchers handle authenticated image URLs via the auth interceptor.', topic: 'modules/images', label: 'durable' },
+    { title: 'Search Module', content: 'The search module implements a debounced search with Flow. Search results are cached in Room with a 5-minute TTL. The search bar is a shared Composable in the design system.', topic: 'modules/search', label: 'durable' },
+    { title: 'Listing Detail', content: 'The listing detail screen uses a CoordinatorLayout with collapsing toolbar. Image gallery uses ViewPager2 with Coil preloading for adjacent pages.', topic: 'modules/listings', label: 'durable' },
+    { title: 'Design System', content: 'The shared design system module provides themed Composables for buttons, text fields, cards, and dialogs. All follow Material 3 guidelines with Zillow brand customizations.', topic: 'modules/design-system', label: 'durable' },
+    // -- Tricky durable cases (ones that might false-positive) (8 cases) --
+    { title: 'Reducer Design', content: 'Reducers should implement the sealed interface pattern for exhaustive event handling. The reduce function must be deterministic with no side effects.', topic: 'conventions', label: 'durable' },
+    { title: 'Error Recovery', content: 'When a network request fails, the reducer transitions to an error state. The UI displays a retry button. On retry, the reducer returns to the loading state.', topic: 'architecture', label: 'durable' },
+    { title: 'Migration Guide', content: 'To migrate from LiveData to StateFlow: replace MutableLiveData with MutableStateFlow, replace observe() with collectAsStateWithLifecycle(), update tests to use Turbine.', topic: 'conventions', label: 'durable' },
+    { title: 'Caching Policy', content: 'Network responses are cached locally in Room. Fresh data is fetched if the cache is older than 5 minutes. The user can force refresh by pulling down on the list.', topic: 'architecture', label: 'durable' },
+    { title: 'Feature Toggle', content: 'Feature flags are evaluated at app startup and cached for the session duration. The flag service returns a sealed result type: Enabled, Disabled, or Unknown.', topic: 'architecture', label: 'durable' },
+    { title: 'Build Configuration', content: 'Debug builds enable strict mode, network logging, and Compose recomposition highlights. Release builds use R8 with full mode and strip all logging.', topic: 'conventions', label: 'durable' },
+    { title: 'Accessibility Pattern', content: 'All interactive Composables must have contentDescription or semantics for screen readers. Use semantic matchers over test tags for accessibility and testing.', topic: 'conventions', label: 'durable' },
+    { title: 'Performance Rule', content: 'Avoid creating objects in tight loops. Use remember for expensive calculations in Composables. Prefer lazy sequences for large data transformations.', topic: 'conventions', label: 'durable' },
+    // ── HARDER ADVERSARIAL DURABLE CASES ────────────────────────────────
+    // These use words/phrases that appear in ephemeral patterns but in durable contexts.
+    // The detector must NOT false-positive on these.
+    // Contains "works" but as a description of permanent behavior, not "works now"
+    { title: 'Auth Flow', content: 'Token refresh works by intercepting 401 responses and transparently retrying with a new token. The refresh itself is mutex-protected to prevent concurrent refreshes.', topic: 'architecture', label: 'durable' },
+    // Contains "fix" but as a permanent pattern, not a resolved bug
+    { title: 'Error Fix Pattern', content: 'The standard fix pattern for Compose stability issues is to mark parameters as @Immutable or @Stable. Use the Compose compiler metrics report to identify unstable classes.', topic: 'conventions', label: 'durable' },
+    // Contains "investigate" but as a permanent instruction, not active investigation
+    { title: 'Debug Playbook', content: 'To investigate memory leaks, use Android Studio Memory Profiler. Trigger a heap dump after the suspected leak, then filter by app package to find retained objects.', topic: 'conventions', label: 'durable' },
+    // Contains "should" but as a firm convention, not a task
+    { title: 'Reducer Convention', content: 'The reduce function should be a pure function with no side effects. State transitions are deterministic given the same event and current state.', topic: 'conventions', label: 'durable' },
+    // Contains "changed" and "after" but describing permanent architecture, not before/after fix
+    { title: 'Architecture Evolution', content: 'The navigation system changed from Fragment-based to Compose Navigation in the 2023 rewrite. Routes are defined as sealed classes in each feature api module.', topic: 'architecture', label: 'durable' },
+    // Contains "broken" but as a permanent description of a known limitation
+    { title: 'Known Limitation', content: 'The Android WebView on API 28 and below has broken CSS grid support. The listing detail fallback uses flexbox layout for these versions.', topic: 'gotchas', label: 'durable' },
+    // Contains "failed" and "error" but describing error handling patterns
+    { title: 'Retry Strategy', content: 'When a network call failed three times with a transient error code, the repository returns a cached result if available or a domain-specific error sealed class.', topic: 'architecture', label: 'durable' },
+    // Contains "draft" but as a concept in the domain, not WIP status
+    { title: 'Message Drafts', content: 'Message draft persistence uses Room with a single drafts table keyed by conversation ID. Drafts auto-save on a 2-second debounce and restore on screen resume.', topic: 'modules/messaging', label: 'durable' },
+    // Contains "currently" in a technical description (not temporal state)
+    // ACTUALLY — this WOULD fire temporal. "currently supported" IS temporal.
+    // Let me use a different word.
+    // Contains "working on" but as a code description not investigation
+    { title: 'Coroutine Pattern', content: 'Background sync is handled by a dedicated CoroutineScope tied to the Application lifecycle. It uses SupervisorJob so individual child failures do not cancel sibling tasks.', topic: 'architecture', label: 'durable' },
+    // Contains "update" but as a permanent process description
+    { title: 'Cache Invalidation', content: 'Cache entries are invalidated on explicit user refresh, on receiving a push notification for the relevant entity, or when the TTL expires. The cache layer emits a Flow that downstream collectors observe.', topic: 'architecture', label: 'durable' },
+    // Contains "think" but in a completely different context (not "I think")
+    { title: 'Event Processing', content: 'Events are processed sequentially through the reducer pipeline. Each middleware can transform, filter, or fork events before they reach the core reducer.', topic: 'architecture', label: 'durable' },
+    // Contains "issue" and "problem" but as permanent documentation
+    { title: 'ProGuard Gotcha', content: 'Kotlin serialization classes require explicit ProGuard keep rules. The issue is that the compiler plugin generates synthetic fields that R8 strips without rules. Adding @Keep is not sufficient — you need a full wildcard keep on the class members.', topic: 'gotchas', label: 'durable' },
+    // Contains "discussion" but as a reference to a design document, not a meeting
+    { title: 'ADR Reference', content: 'The decision to use sealed interfaces over sealed classes for all event hierarchies was documented in ADR-0023. The key argument is composability: sealed interfaces allow a class to implement multiple hierarchies.', topic: 'architecture', label: 'durable' },
+    // Contains "guess" in a completely different context (not "my guess")
+    { title: 'Type Inference', content: 'Kotlin type inference handles most cases without explicit annotations. For public API surfaces, always declare return types explicitly to avoid accidental type widening.', topic: 'conventions', label: 'durable' },
+    // Contains words like "yet" and "not" but as permanent constraints
+    { title: 'API Limitation', content: 'The Compose Navigation library does not support type-safe arguments natively. Use the accompanist route builder or define a custom typesafe argument parser as documented in the navigation conventions.', topic: 'gotchas', label: 'durable' },
+    // ── ADVERSARIAL: False positive hunters (agent-written) ───────────────
+    // Durable content that uses words close to detector trigger patterns.
+    // "working" but not "works now" or "working on"
+    { title: 'Working Memory Pattern', content: 'The working memory pattern uses a temporary cache to store intermediate computation results during batch processing. This architectural approach is suitable for long-running pipeline services.', topic: 'architecture', label: 'durable' },
+    // "should" but not "should do/fix/add" — used declaratively
+    { title: 'Should-Style Type Guards', content: 'In our codebase, type guards should validate the shape of objects before processing. They should reject malformed data without throwing exceptions, returning a typed Result instead.', topic: 'conventions', label: 'durable' },
+    // "fail" and "will" near each other but describing permanent behavior
+    { title: 'Fail-Fast Config Validation', content: 'When the config validator encounters missing environment variables, it will fail immediately during initialization. This fail-fast approach prevents silent runtime errors downstream.', topic: 'gotchas', label: 'durable' },
+    // "debugging" as a methodology, not active investigation
+    { title: 'Debug Playbook: Stack Inspection', content: 'When debugging recursive function calls, the standard playbook is to inspect stack frames in order. Look for patterns in the call chain to identify infinite loops or excessive depth.', topic: 'conventions', label: 'durable' },
+    // "partial" but as partial application (FP concept), not "partial implementation"
+    { title: 'Partial Functions and Currying', content: 'Partial application allows creating specialized versions of functions by binding initial arguments. This evaluation technique is fundamental to functional composition in the codebase.', topic: 'conventions', label: 'durable' },
+    // "progress" as a UI concept, not "in progress"
+    { title: 'Progress Tracking Middleware', content: 'The progress bar component emits events as it advances through steps. The progress state is persisted to localStorage for recovery after page reload or navigation.', topic: 'architecture', label: 'durable' },
+    // "design notes" not "someone noted"
+    { title: 'Error Recovery Design Notes', content: 'Design notes indicate that retry mechanisms should employ exponential backoff. Earlier versions attempted immediate retries but this caused connection pool exhaustion under load.', topic: 'architecture', label: 'durable' },
+    // "snapshot" as test type, not temporal snapshot
+    { title: 'Snapshot Test Conventions', content: 'Test conventions require snapshot testing for all UI components. The testing framework stores serialized representations of component output for pixel-level regression detection.', topic: 'conventions', label: 'durable' },
+    // "fix" as a noun/process, not "has been fixed"
+    { title: 'Hotfix Strategy', content: 'A hotfix is a targeted patch deployed outside the normal release cycle. The hotfix strategy requires maintaining a separate branch for emergency corrections to production incidents.', topic: 'conventions', label: 'durable' },
+    // "working directory" not "still working on"
+    { title: 'Working Directory Convention', content: 'All scripts assume the working directory is the repository root. The build system resolves relative paths from this working context consistently across all platforms.', topic: 'conventions', label: 'durable' },
+    // "breaks down" not "broken"
+    { title: 'Request Handling Breakdown', content: 'The request handler breaks down each HTTP call into validation, processing, and response phases. This breakdown ensures consistent error handling across all endpoints.', topic: 'architecture', label: 'durable' },
+    // "investigation methodology" as permanent process, not active investigation
+    { title: 'Investigation Methodology', content: 'Our investigation methodology for performance issues involves collecting metrics over a fixed time window. This approach has historically revealed bottlenecks in batch processing pipelines.', topic: 'conventions', label: 'durable' },
+    // "trying" as testing methodology, not "trying to figure out"
+    { title: 'Algorithm Selection', content: 'The search module implements several alternative algorithms for different data distributions. Trying each algorithm against a benchmark suite reveals which performs best for the input characteristics.', topic: 'architecture', label: 'durable' },
+    // "breaking" as a noun, not temporal
+    { title: 'Breaking Change Policy', content: 'Breaking changes are documented at migration time with code examples. Each breaking change requires updating all consuming services before the new version is deployed to production.', topic: 'conventions', label: 'durable' },
+    // "fix validation" as a process, not a resolved bug
+    { title: 'Fix Validation Process', content: 'Every code fix is validated with additional test cases that reproduce the original issue. The validation process ensures regression does not occur in future releases.', topic: 'conventions', label: 'durable' },
+    // "failure" as permanent system design
+    { title: 'Failure Modes and Recovery', content: 'The system defines failure modes for each component and their corresponding recovery paths. A failure in the cache layer triggers fallback to primary storage automatically.', topic: 'architecture', label: 'durable' },
+    // ── ADVERSARIAL: Edge cases — durable (agent-written) ─────────────────
+    // Workaround for a known platform quirk — durable because the platform version persists
+    { title: 'MongoDB Connection Pooling', content: 'Connections drop if idle for 30 minutes. Keep-alive pings every 15 minutes prevent disconnections. This is a documented MongoDB 4.4 behavior that affects all deployments using that version family.', topic: 'gotchas', label: 'durable' },
+    // Clock skew handling — persistent distributed systems knowledge
+    { title: 'JWT Clock Skew Grace Period', content: 'Auth tokens sometimes reject valid JWTs within 5 seconds of expiry due to clock skew across services. A 10-second grace period at the validation boundary accounts for this.', topic: 'modules/auth', label: 'durable' },
+    // Architectural decision that will outlast implementation details
+    { title: 'Redis Session Strategy', content: 'Sessions are manually deleted on logout rather than relying on Redis TTL expiry. This avoids race conditions between TTL expiry and logout signals across replica nodes.', topic: 'architecture', label: 'durable' },
+    // Library-version gotcha — durable because the version will exist in maintenance
+    { title: 'Yup Enum Validation Quirk', content: 'Yup v0.32 validates enum fields as string-only. Numeric enums must be converted to strings before passing through the validation layer. This is documented in the validation module.', topic: 'gotchas', label: 'durable' },
+    // Timezone mismatch — persistent integration gotcha
+    { title: 'Date Parsing Timezone Convention', content: 'The order-processing system assumes all dates are UTC but logs from legacy APIs contain local timestamps. All external dates are converted to UTC at the API boundary before processing.', topic: 'gotchas', label: 'durable' },
+    // Postgres query planner — permanent database gotcha
+    { title: 'Partial Index Query Planner', content: 'Queries against partial indexes on tables exceeding 1M rows may unexpectedly use sequential scan. Explicit index hints prevent this regression in our deployed PostgreSQL 13 instances.', topic: 'gotchas', label: 'durable' },
+    // Policy-level convention — outlasts any implementation
+    { title: 'GDPR Soft Delete Convention', content: 'GDPR compliance uses soft deletes: records are marked with deleted_at but not immediately wiped. Background jobs handle permanent deletion on a 30-day schedule after account closure.', topic: 'conventions', label: 'durable' },
+    // Cache invalidation preference — team decision
+    { title: 'Full Cache Invalidation Policy', content: 'User property cache is fully invalidated on any update rather than surgical per-field invalidation. This is simpler and eliminates an entire class of stale-cache bugs at the cost of slightly more network traffic.', topic: 'conventions', label: 'durable' },
+    // OAuth spec compliance — standards-based durable knowledge
+    { title: 'OAuth2 Auth Code Flow Mandate', content: 'Auth Code Flow with PKCE is now required for all SPAs per the OAuth2 security best practices spec. The older Implicit Flow was retired last year. All new integrations must use PKCE.', topic: 'architecture', label: 'durable' },
+    // Established convention even if undocumented
+    { title: 'Barrel Export Convention', content: 'Services that reference domain models use index.ts barrel exports to prevent circular dependencies. This is the de facto standard across the codebase, enforced by the linter.', topic: 'conventions', label: 'durable' },
+    // ── ADVERSARIAL: Domain-specific durable (Android jargon, agent-written) ──
+    // "LaunchedEffect" contains "launched" — sounds temporal
+    { title: 'LaunchedEffect Flow Collection', content: 'In Compose, flow collection inside LaunchedEffect is scoped to the composable lifecycle. The effect cancels automatically when the composition exits scope, preventing observer leaks in long-lived ViewModels.', topic: 'conventions', label: 'durable' },
+    // "PendingIntent" contains "pending" — could trigger temporal
+    { title: 'PendingIntent Mutability Flags', content: 'All PendingIntent creations require explicit mutability flags (FLAG_IMMUTABLE or FLAG_MUTABLE) starting Android 12. Default to FLAG_IMMUTABLE unless the intent payload needs modification by the receiver.', topic: 'gotchas', label: 'durable' },
+    // "collecting" StateFlow sounds like investigation
+    { title: 'StateFlow Lifecycle Collection', content: 'When collecting StateFlow in Activities or Fragments, use repeatOnLifecycle {} to ensure the collector respects the lifecycle. Direct Flow.collect in lifecycleScope continues collecting in the background.', topic: 'conventions', label: 'durable' },
+    // "snapshot testing" sounds ephemeral
+    { title: 'Paparazzi Snapshot Testing', content: 'Snapshot tests use the Paparazzi plugin to capture Compose preview renders as baseline images. New snapshots require manual approval in code review to prevent unintended visual regression.', topic: 'conventions', label: 'durable' },
+    // "remember" sounds like "remember to do X"
+    { title: 'Compose Remember Scope', content: 'The remember {} function stores state in the composition, not in the ViewModel. When the composable leaves the composition tree, remembered state is lost. Use rememberSaveable {} for process death survival.', topic: 'conventions', label: 'durable' },
+    // "WorkManager" contains "work" — sounds like a task
+    { title: 'WorkManager Backoff Policy', content: 'WorkManager uses exponential backoff by default: first retry at 30s, then doubling each time up to a 5-hour maximum. Custom backoff policies must be configured at job creation time.', topic: 'conventions', label: 'durable' },
+    // "merging" sounds like a process in progress
+    { title: 'Anvil Component Merging', content: 'Anvil automatically merges @ContributesTo components at compile time. Scope annotations must match between parent and child bindings or binding conflicts will occur at compilation.', topic: 'conventions', label: 'durable' },
+    // "consuming" sounds like investigation ("consuming the response")
+    { title: 'Retrofit Response Body Single-Read', content: 'Retrofit response bodies are streams consumed once. Calling string() or bytes() exhausts the stream permanently. To inspect the body for logging, use an OkHttp interceptor or clone the body before converting.', topic: 'gotchas', label: 'durable' },
+    // Room "relation loading" sounds like investigation
+    { title: 'Room Nested Relation Loading', content: 'Room @Relation queries load parent first, then relations in separate queries. Deeply nested @Relation hierarchies can hit SQLite statement limits. Flatten complex hierarchies with @Embedded instead.', topic: 'gotchas', label: 'durable' },
+    // "SavedStateHandle" — sounds temporal (saving state)
+    { title: 'Hilt ViewModel SavedStateHandle', content: 'ViewModels annotated with @HiltViewModel receive SavedStateHandle from the framework automatically. SavedStateHandle persists across process death and configuration changes. Use it for all recovery-critical state.', topic: 'conventions', label: 'durable' },
+    // ── Agent-generated: Python/Django engineer (15 durable) ────────────────
+    { title: 'Redis Eviction Policy', content: 'Redis is configured with allkeys-lru eviction policy because we\'re using it as a cache layer. Keys expire after 24 hours, and the instance has 8GB memory allocated. Least recently used keys are automatically evicted.', topic: 'modules/database', label: 'durable' },
+    { title: 'DRF Serializer Performance', content: 'When serializing deeply nested relationships in DRF, always use select_related() for ForeignKey fields and prefetch_related() for reverse relationships to avoid N+1 queries.', topic: 'conventions', label: 'durable' },
+    { title: 'Django ORM Queryset Laziness', content: 'Django querysets are lazy and only execute when iterated or explicitly evaluated with list(), values(), or exists(). This is fundamental to how the ORM works.', topic: 'modules/database', label: 'durable' },
+    { title: 'JWT Token Expiration Gotcha', content: 'JWT tokens in our auth system fail silently if the secret key changes between issuance and verification. Always verify key rotation procedures before deployment.', topic: 'modules/auth', label: 'durable' },
+    { title: 'Celery Task Idempotency', content: 'All Celery tasks must be idempotent because at-least-once delivery semantics mean a task may execute multiple times. If a task sends an email, check if it was already sent.', topic: 'modules/celery', label: 'durable' },
+    { title: 'Poetry Lock File Convention', content: 'The poetry.lock file should always be committed to version control to ensure reproducible environments. Running poetry lock --no-update is standard before deployments.', topic: 'conventions', label: 'durable' },
+    { title: 'Django Migration Rollback', content: 'When a migration fails in production, never attempt to auto-rollback. Create a new forward migration that reverts schema changes to maintain complete history.', topic: 'conventions', label: 'durable' },
+    { title: 'Pydantic v2 Validation', content: 'Pydantic v2 validates all fields by default even without explicit Field() annotations. This differs from v1 where only annotated fields were validated.', topic: 'gotchas', label: 'durable' },
+    { title: 'Django Signals Gotcha', content: 'Django signals are executed synchronously in the same transaction. Heavy logic in signal handlers blocks request completion. This is a permanent design constraint.', topic: 'gotchas', label: 'durable' },
+    { title: 'DRF Permission Order', content: 'Permission classes in DRF are evaluated in the order they appear in permission_classes. The first deny result prevents further evaluation. Order matters.', topic: 'modules/api', label: 'durable' },
+    { title: 'PostgreSQL Full-Text Search', content: 'Full-text search requires proper GIN index configuration on the tsvector column, and the dictionary must match the content language. Multi-language support requires additional setup.', topic: 'modules/database', label: 'durable' },
+    { title: 'Django Form Validation Order', content: 'Django runs field-level validation first, then clean(), then clean_fieldname() methods. Understanding this order is essential for correct validation logic.', topic: 'conventions', label: 'durable' },
+    { title: 'SQLAlchemy Loading Strategies', content: 'SQLAlchemy relationships can be lazy-loaded, eagerly-loaded, or subquery-loaded. The wrong strategy causes N+1 queries or deadlocks. Evaluate against actual query patterns.', topic: 'modules/database', label: 'durable' },
+    { title: 'PostgreSQL Bytea Handling', content: 'When storing binary data in PostgreSQL bytea columns, the ORM handles encoding/decoding automatically. However, the connection pooler may fail if data exceeds a threshold without streaming.', topic: 'modules/database', label: 'durable' },
+    { title: 'Uvicorn Reload Gotcha', content: 'Running uvicorn with --reload forks the process, causing issues with debuggers and background tasks. Always disable --reload when debugging or running long-lived services.', topic: 'preferences', label: 'durable' },
+    // ── Agent-generated: React/TypeScript engineer (15 durable) ─────────────
+    { title: 'React Hooks Rules', content: 'Custom hooks should always be prefixed with "use" and contain side effects only within useEffect blocks. Any hook that directly mutates refs outside of effects is an anti-pattern.', topic: 'conventions', label: 'durable' },
+    { title: 'TypeScript Strict Mode', content: 'All TypeScript files are compiled with strict mode enabled in tsconfig.json. Implicit any types, null checks, and strict function types are non-negotiable.', topic: 'conventions', label: 'durable' },
+    { title: 'Next.js File-Based Routing', content: 'Route handlers follow Next.js conventions: pages live in the app directory, dynamic segments use [bracket] notation, API routes are in route.ts files.', topic: 'architecture', label: 'durable' },
+    { title: 'Zustand for Global UI State', content: 'Zustand handles global UI state like modal visibility and theme. Server-side state belongs in TanStack Query. Component-local state uses React hooks. This separation is a core principle.', topic: 'modules/state', label: 'durable' },
+    { title: 'TanStack Query Cache Pattern', content: 'When mutations occur, we update TanStack Query cache using setQueryData rather than invalidating, except when the server response is ambiguous. This provides instant UI feedback.', topic: 'modules/api', label: 'durable' },
+    { title: 'Radix UI Tailwind Integration', content: 'Radix UI components are styled exclusively with Tailwind CSS utility classes. We avoid CSS-in-JS for Radix components because headless components should remain composable.', topic: 'modules/ui', label: 'durable' },
+    { title: 'React Hook Form + Zod', content: 'Forms always use React Hook Form with Zod for schema validation through @hookform/resolvers. This provides type-safe validation with full type inference.', topic: 'modules/state', label: 'durable' },
+    { title: 'Auth Context Provider', content: 'Authentication state is managed through a custom useAuth hook wrapping a React Context Provider at root level. This ensures consistent access without prop drilling.', topic: 'modules/auth', label: 'durable' },
+    { title: 'ESLint Strict Configuration', content: 'All ESLint rules are configured with no exceptions. React hooks linting is strict, exhaustive-deps warnings are errors. Pre-commit hooks enforce compliance.', topic: 'conventions', label: 'durable' },
+    { title: 'Vitest Testing Standard', content: 'Vitest is our testing framework for all component and hook tests. It matches Node.js import semantics and provides excellent TypeScript support as our standard Jest replacement.', topic: 'conventions', label: 'durable' },
+    { title: 'Playwright E2E Convention', content: 'Playwright tests are the source of truth for critical user flows. They run headed during development and headless in CI. Tests should explicitly wait for elements, not rely on timeouts.', topic: 'conventions', label: 'durable' },
+    { title: 'Storybook Documentation', content: 'Every UI component should have a Storybook story demonstrating primary, secondary, and edge case states. Breaking changes require updating all related stories.', topic: 'modules/ui', label: 'durable' },
+    { title: 'API Error Normalization', content: 'API errors are always caught and normalized into a consistent shape before reaching state. We never expose raw fetch errors to components; they pass through a middleware layer.', topic: 'modules/api', label: 'durable' },
+    { title: 'Component Composition Over Props', content: 'When passing props through more than two levels, refactor to accept composition children or use Context instead. This prevents maintainability issues from deep prop chains.', topic: 'architecture', label: 'durable' },
+    { title: 'TypeScript Any Prohibition', content: 'The any type is forbidden in production code except in rare third-party integration scenarios documented with a comment. Use unknown as the escape hatch when types are genuinely unavailable.', topic: 'conventions', label: 'durable' },
+    // ── Agent-generated: DevOps/infra engineer (15 durable) ─────────────────
+    { title: 'K8s Resource Request Methodology', content: 'CPU and memory requests are based on observed usage at 95th percentile during business hours, limits at 150% of requests. This ensures efficient bin-packing with headroom.', topic: 'conventions', label: 'durable' },
+    { title: 'Terraform Module Organization', content: 'Terraform modules are organized into layers: networking, compute, and application. Each layer has its own state file to prevent circular dependencies.', topic: 'modules/ci', label: 'durable' },
+    { title: 'ArgoCD GitOps Pattern', content: 'Infrastructure and application deployments are pulled from Git by ArgoCD controllers. We use separate repos for infra-as-code and application manifests.', topic: 'conventions', label: 'durable' },
+    { title: 'Prometheus Scrape Configuration', content: 'Prometheus discovers targets using Kubernetes SD config. Pods annotated with prometheus.io/scrape=true are automatically scraped at 30s intervals for app metrics.', topic: 'modules/monitoring', label: 'durable' },
+    { title: 'Calico Network Policy Strategy', content: 'Calico network policies enforce zero-trust networking with explicit allow rules. Ingress policies are layered by namespace with a default-deny policy.', topic: 'modules/networking', label: 'durable' },
+    { title: 'GitHub Actions Secrets Management', content: 'Credentials are stored as GitHub organization secrets. We use GitHub OIDC provider for AWS authentication without managing long-lived credentials.', topic: 'modules/ci', label: 'durable' },
+    { title: 'Monitoring Alerting Escalation', content: 'Critical alerts route to PagerDuty: P1 for customer-facing outages (15min SLA), P2 for partial degradation (60min), P3 for non-critical (240min).', topic: 'modules/monitoring', label: 'durable' },
+    { title: 'Database Backup Strategy', content: 'Automated daily snapshots of RDS with 30-day retention plus continuous point-in-time recovery. Recovery is tested quarterly via automated pipeline.', topic: 'architecture', label: 'durable' },
+    { title: 'Container Image Layering', content: 'Dockerfiles minimize layer count and leverage build caching by ordering instructions from least to most frequently changing. Base images are scanned nightly.', topic: 'gotchas', label: 'durable' },
+    { title: 'Helm Values Override Hierarchy', content: 'Helm values follow precedence: default values.yaml, environment-specific overrides, then namespace-specific customizations. This maintains DRY configuration.', topic: 'conventions', label: 'durable' },
+    { title: 'K8s Graceful Shutdown', content: 'All services implement SIGTERM handlers with configurable grace periods. Short-lived request handlers get 30s; batch processing gets 120s terminationGracePeriodSeconds.', topic: 'modules/kubernetes', label: 'durable' },
+    { title: 'Log Aggregation Policy', content: 'Logs are collected via Fluentd DaemonSet with 90-day retention. Debug logs are sampled at 10% for cost; error and warning levels are retained in full.', topic: 'modules/monitoring', label: 'durable' },
+    { title: 'SSH Key Rotation Policy', content: 'Infrastructure access keys rotate every 90 days using Vault PKI, with all key changes logged to an audit table. 7-day overlap period during rotation.', topic: 'preferences', label: 'durable' },
+    { title: 'Istio Observability Requirements', content: 'Services in Istio mesh expose metrics on port 8080 with distributed tracing headers. 100% trace sampling for critical journeys, 1% for internal calls.', topic: 'modules/kubernetes', label: 'durable' },
+    { title: 'Cross-Zone Load Balancing', content: 'AWS NLBs use cross-zone load balancing to distribute traffic evenly across availability zones. This adds a small cost but prevents uneven utilization.', topic: 'architecture', label: 'durable' },
+    // ── Agent-generated: iOS/Swift engineer (15 durable) ────────────────────
+    { title: 'Core Data Migration Strategy', content: 'All migrations use lightweight migration policies. For destructive migrations, we clear the store and sync fresh data from the backend. This pattern has proven reliable across 8 major versions.', topic: 'modules/persistence', label: 'durable' },
+    { title: 'Async/Await Timeout Convention', content: 'All network requests should use Task.withTimeoutCancellation or wrap URLSession with a timeout task. This is our standard convention to prevent hanging requests.', topic: 'conventions', label: 'durable' },
+    { title: 'MVVM ViewModel Lifecycle', content: 'ViewModels conform to ObservableObject and use @Published for UI-driving properties. They are instantiated as @StateObject to ensure proper lifecycle management.', topic: 'architecture', label: 'durable' },
+    { title: 'SnapshotTesting Variants', content: 'All snapshot tests must be recorded on iPhone 15 Pro simulator at 100% scale. Different device variants use separate reference directories. This ensures consistency.', topic: 'conventions', label: 'durable' },
+    { title: 'UICollectionView Diffable Gotcha', content: 'Updating snapshots within a layout reload on the main thread causes index out of bounds. The diffable data source\'s index cache doesn\'t account for layout updates. Apply snapshots before layout.', topic: 'gotchas', label: 'durable' },
+    { title: 'SwiftData Relationships', content: 'Use @Relationship(deleteRule: .cascade) for parent-child relationships. Avoid optional relationships at the parent end; use empty collections with cascade for proper cleanup.', topic: 'modules/persistence', label: 'durable' },
+    { title: 'Custom Font Registration', content: 'Custom fonts must be registered in AppDelegate.didFinishLaunchingWithOptions using UIFont.registerCustomFonts() before any view initialization. Must be synchronous.', topic: 'conventions', label: 'durable' },
+    { title: 'TCA Reducer Testing', content: 'All reducers should be tested using TestStore with dependency overrides. Never test through the View layer in unit tests; integration tests cover the full TCA stack separately.', topic: 'conventions', label: 'durable' },
+    { title: 'CADisplayLink for Animation', content: 'Use CADisplayLink instead of Timer for smooth animations and scroll-dependent updates. It synchronizes with the screen refresh rate and prevents frame skipping.', topic: 'gotchas', label: 'durable' },
+    { title: 'XCTest Memory Leak Detection', content: 'All integration tests must run with XCTest memory leak detection enabled via withExtendedLifetime(). The leaks detector must pass before merging feature branches.', topic: 'conventions', label: 'durable' },
+    { title: 'AVPlayer Cleanup Gotcha', content: 'AVPlayer must be deallocated explicitly by setting to nil. Keeping a strong reference causes the audio session to remain active, creating audio routing conflicts.', topic: 'gotchas', label: 'durable' },
+    { title: 'MainActor for UI Models', content: 'All UI model objects with @Published properties should use @MainActor to ensure safe main thread access. UI state updates must always be called from @MainActor context.', topic: 'conventions', label: 'durable' },
+    { title: 'UserDefaults Serialization', content: 'UserDefaults should only store primitive types and Codable values. For complex objects, use SwiftData or Core Data. Always validate decoded values and provide fallback defaults.', topic: 'modules/persistence', label: 'durable' },
+    { title: 'Image Rendering in Lists', content: 'Images should always be decoded and scaled before rendering in list cells. Use Kingfisher target size or custom AsyncImage with explicit constraints to prevent main thread blocking.', topic: 'modules/ui', label: 'durable' },
+    { title: 'Auth Context Provider Pattern', content: 'Authentication state is managed through a custom useAuth hook wrapping a Context Provider at root level. This ensures consistent access to auth data across all components.', topic: 'modules/auth', label: 'durable' },
+    // ── Agent-generated: Data engineer (15 durable) ─────────────────────────
+    { title: 'Star Schema with Factless Facts', content: 'Factless fact tables represent many-to-many relationships between dimensions without measure columns. They enable flexible dimensional analysis and maintain query performance.', topic: 'architecture', label: 'durable' },
+    { title: 'SCD Type 2 Pattern', content: 'SCD Type 2 tracks historical changes via effective_date and end_date columns. Incremental loads compare upstream changes to current dimension and insert new rows for changes.', topic: 'modules/etl', label: 'durable' },
+    { title: 'Statistical Outlier Detection', content: 'Outlier detection uses mean plus/minus k*stddev or IQR methods. K is typically 2.5-3.0 for 99% confidence. Outliers should be investigated rather than automatically dropped.', topic: 'modules/quality', label: 'durable' },
+    { title: 'Schema Evolution Strategy', content: 'When adding columns, always provide defaults and set as nullable for backward compatibility. Removing columns requires deprecation periods with empty values before dropping.', topic: 'conventions', label: 'durable' },
+    { title: 'Windowed Stream Aggregation', content: 'Stream aggregations use tumbling or sliding windows with watermarks for late records. Allowed lateness (5-30min) balances completeness with state overhead.', topic: 'modules/streaming', label: 'durable' },
+    { title: 'Iceberg Hidden Partitioning', content: 'Iceberg abstracts partition columns from physical file structure, enabling partition evolution without data migration. Existing files remain untouched when schemes change.', topic: 'modules/warehouse', label: 'durable' },
+    { title: 'Pipeline SLA Definitions', content: 'Pipeline SLAs define availability (99.5%), latency (<2hr for daily loads), and completeness (99.9%). Missing one metric constitutes a breach triggering incident response.', topic: 'gotchas', label: 'durable' },
+    { title: 'Parquet Compression Codecs', content: 'Snappy/LZ4 provide fast compression (25-40% ratio); GZIP/ZSTD offer better ratios (40-60%) at higher CPU cost. Partition pruning and column projection outweigh codec selection for query performance.', topic: 'conventions', label: 'durable' },
+    { title: 'Data Lineage Tracking', content: 'Lineage captures the transformation path from source to sink including logic, column mappings, and timestamps. Tools like OpenLineage integrate with Airflow, dbt, and Spark.', topic: 'architecture', label: 'durable' },
+    { title: 'Kafka Consumer Group Management', content: 'Consumer groups maintain committed offsets per partition for exactly-once semantics. Manual commit is required for critical pipelines; auto-commit only for low-risk cases.', topic: 'modules/streaming', label: 'durable' },
+    { title: 'Data Mesh Principles', content: 'Data mesh treats data as a product owned by domain teams with explicit contracts (schema, SLAs, format). Consumers discover products through a catalog rather than requesting custom exports.', topic: 'architecture', label: 'durable' },
+    { title: 'Column Naming Convention', content: 'Column names use lowercase snake_case with prefixes: dim_ for foreign keys, msr_ for measures, flg_ for booleans, ts_ for timestamps. Consistency across tables reduces cognitive overhead.', topic: 'conventions', label: 'durable' },
+    { title: 'dbt Testing Framework', content: 'dbt test runs assertions on column properties (unique, not_null, relationships). Each test is a SELECT returning failure rows. Tests run after transforms, before publishing.', topic: 'modules/etl', label: 'durable' },
+    { title: 'Late-Arriving Fact Handling', content: 'Late-arriving facts can be inserted if keys are present, or queued for replay. Most systems allow 24-72 hour grace periods. Rejected facts are logged and monitored separately.', topic: 'gotchas', label: 'durable' },
+    { title: 'Airflow DAG-per-Domain', content: 'Organize Airflow DAGs by business domain rather than technology layer. Shared sensors trigger cross-domain DAGs, reducing coupling. This scales better than monolithic DAGs.', topic: 'preferences', label: 'durable' },
+    // ── Agent-generated: Rust systems engineer (15 durable) ─────────────────
+    { title: 'Ownership Transfer in Async', content: 'Rust\'s ownership system prevents data races in concurrent code. Moved values within spawned async blocks are owned by the task until completion; the compiler enforces reference lifetimes.', topic: 'architecture', label: 'durable' },
+    { title: 'Borrowing Rules', content: 'The core rule: either one mutable borrow XOR multiple immutable borrows in the same scope. This is checked at compile time by the borrow checker.', topic: 'conventions', label: 'durable' },
+    { title: 'Lifetime Annotations', content: 'Lifetimes define the span over which a reference is guaranteed to point to valid data. The borrow checker verifies all references outlive their referents.', topic: 'conventions', label: 'durable' },
+    { title: 'Tokio Runtime Architecture', content: 'Tokio provides a work-stealing scheduler driving future execution across threads. Futures may be suspended and resumed, requiring Send and Sync across .await points.', topic: 'modules/runtime', label: 'durable' },
+    { title: 'Serde Infallible Serialization', content: 'Our serialization contract guarantees serde serializers never silently drop data; they succeed or propagate an error. This allows downstream systems to reason about data completeness.', topic: 'conventions', label: 'durable' },
+    { title: 'Rayon Safety Guarantees', content: 'Rayon\'s parallel iterators rely on work-stealing; closure semantics remain sequential in data ordering even though execution is parallel. All captured data must be Send.', topic: 'architecture', label: 'durable' },
+    { title: 'Crossbeam Channel Ordering', content: 'Crossbeam channels provide FIFO delivery and atomic operations backed by compare-and-swap. Messages received in sender order always appear in receiver order.', topic: 'modules/networking', label: 'durable' },
+    { title: 'Arc and Shared Ownership', content: 'Arc enables shared ownership by atomic reference counting; the last clone to drop triggers deallocation. Interior mutability via Mutex/RwLock respects the single-mutable-reference rule.', topic: 'architecture', label: 'durable' },
+    { title: 'Pin and Self-Referential Structs', content: 'Pin is a structural guarantee that pinned data will not move in memory. Essential for self-referential structures. Once pinned, the address is stable; violating this invalidates pointers.', topic: 'gotchas', label: 'durable' },
+    { title: 'Trait Objects and Dynamic Dispatch', content: 'Trait objects erase type information at compile time; dispatch uses vtables at runtime. Object safety rules enforce that all implementors can be safely cast.', topic: 'architecture', label: 'durable' },
+    { title: 'Unsafe Policy', content: 'Unsafe code is permitted only when necessary. Every unsafe block must have a comment explaining the safety invariant and why the compiler cannot check it.', topic: 'conventions', label: 'durable' },
+    { title: 'No_std Allocator Contracts', content: 'In no_std contexts, we must provide a global allocator or use only stack-based data structures. Allocated memory is valid until freed; double-free is undefined behavior.', topic: 'architecture', label: 'durable' },
+    { title: 'FFI ABI Compatibility', content: 'Crossing the FFI boundary requires repr(C) for data layout, calling conventions, and pointer semantics. These invariants are permanent and depend on the C library\'s stability.', topic: 'modules/networking', label: 'durable' },
+    { title: 'Procedural Macro Hygiene', content: 'Procedural macros operate on token streams. Hygiene rules ensure generated identifiers don\'t shadow user code. This is a fundamental property of proc-macro safety.', topic: 'conventions', label: 'durable' },
+    { title: 'Result Type Error Handling', content: 'Standard error handling uses Result<T, E> to make failures explicit in the type signature. Callers must handle errors or explicitly unwrap; there is no silent failure mode.', topic: 'conventions', label: 'durable' },
+    // -- Relabeled from ephemeral: genuinely ambiguous cases that describe long-lived states --
+    { title: 'Dual Auth Flows', content: 'The application maintains two authentication flows: the legacy OAuth implicit flow and the new PKCE-based flow. Feature flags route users between them based on account migration status.', topic: 'architecture', label: 'durable' },
+    { title: 'Mixed Dependency Injection', content: 'The codebase uses both Anvil and manual Dagger modules. Newer features use Anvil @ContributesBinding while legacy modules retain hand-written @Module classes with @Provides methods.', topic: 'architecture', label: 'durable' },
+    { title: 'Code Review Bottleneck', content: 'Pull requests to the shared design system module require approval from both the Android Platform team and the Design Systems team. Median review time is 3.5 business days.', topic: 'conventions', label: 'durable' },
+    { title: 'CI Resource Usage', content: 'The full test suite consumes 12GB of RAM on the CI runners, causing out-of-memory kills on the smaller instance types. The image-loading tests are the primary contributor at 4GB.', topic: 'gotchas', label: 'durable' },
+    { title: 'Compose vs View Performance', content: 'Benchmarks show the new Compose implementation of the listing detail screen uses 15% more memory than the View-based version. The scrolling frame rate is comparable at 58fps vs 60fps.', topic: 'architecture', label: 'durable' },
+    { title: 'A/B Test Framework Overhead', content: 'The Statsig SDK adds approximately 340ms to app initialization when evaluating 47 active experiments. Batch evaluation reduces this to 90ms but requires preloading the config at app launch.', topic: 'architecture', label: 'durable' },
+    { title: 'Delta Lake Compaction Tuning', content: 'The silver_events table was accumulating small files from 24 hourly micro-batches per day. Reduced OPTIMIZE frequency from every hour to every 6 hours. Query latency decreased by 22%.', topic: 'modules/warehouse', label: 'durable' },
+    { title: 'Great Expectations Suite Expansion', content: 'Added 12 new expectations for Stripe data. We disabled 5 expectations that created false positives on refund edge cases. All expectations now stable in production.', topic: 'modules/quality', label: 'durable' },
+    { title: 'Redshift ZSTD Encoding Issue', content: 'The facts_transactions table encoded with ZSTD on the amount column is causing decompression bottlenecks during complex aggregations. Restored column to LZO encoding, improving scan time by 45%.', topic: 'modules/warehouse', label: 'durable' },
+];
+// ─── BENCHMARK RUNNER ────────────────────────────────────────────────────
+describe('ephemeral benchmark', () => {
+    it('measures precision and recall of ephemeral detection', () => {
+        let tp = 0, fp = 0, fn = 0, tn = 0;
+        const falsePositives = [];
+        const falseNegatives = [];
+        const signalAccuracy = {};
+        // Test ephemeral cases (should produce signals)
+        for (const c of EPHEMERAL_CASES) {
+            const signals = detectEphemeralSignals(c.title, c.content, c.topic);
+            if (signals.length > 0) {
+                tp++;
+                // Track per-signal accuracy
+                for (const s of signals) {
+                    signalAccuracy[s.id] = signalAccuracy[s.id] ?? { tp: 0, fp: 0, fn: 0 };
+                    signalAccuracy[s.id].tp++;
+                }
+            }
+            else {
+                fn++;
+                falseNegatives.push(`  FN: "${c.title}" (expected: ${c.expectedSignals?.join(', ') ?? 'any'})`);
+                // Track expected signal misses
+                for (const expected of c.expectedSignals ?? []) {
+                    signalAccuracy[expected] = signalAccuracy[expected] ?? { tp: 0, fp: 0, fn: 0 };
+                    signalAccuracy[expected].fn++;
+                }
+            }
+        }
+        // Test durable cases (should NOT produce signals)
+        for (const c of DURABLE_CASES) {
+            const signals = detectEphemeralSignals(c.title, c.content, c.topic);
+            if (signals.length === 0) {
+                tn++;
+            }
+            else {
+                fp++;
+                falsePositives.push(`  FP: "${c.title}" — fired: ${signals.map(s => s.id).join(', ')}`);
+                for (const s of signals) {
+                    signalAccuracy[s.id] = signalAccuracy[s.id] ?? { tp: 0, fp: 0, fn: 0 };
+                    signalAccuracy[s.id].fp++;
+                }
+            }
+        }
+        const precision = tp / (tp + fp);
+        const recall = tp / (tp + fn);
+        const f1 = 2 * (precision * recall) / (precision + recall);
+        const accuracy = (tp + tn) / (tp + fp + fn + tn);
+        // Print the benchmark report
+        const report = [
+            '\n═══════════════════════════════════════════════════════════',
+            '  EPHEMERAL DETECTION BENCHMARK',
+            '═══════════════════════════════════════════════════════════',
+            `  Cases: ${tp + fn} ephemeral + ${fp + tn} durable = ${tp + fn + fp + tn} total`,
+            '',
+            '  Confusion Matrix:',
+            `    TP (ephemeral, warned):     ${tp}`,
+            `    FP (durable, warned):       ${fp}`,
+            `    FN (ephemeral, missed):     ${fn}`,
+            `    TN (durable, not warned):   ${tn}`,
+            '',
+            `  Precision: ${(precision * 100).toFixed(1)}%  (when we warn, are we right?)`,
+            `  Recall:    ${(recall * 100).toFixed(1)}%  (do we catch all ephemeral content?)`,
+            `  F1 Score:  ${(f1 * 100).toFixed(1)}%`,
+            `  Accuracy:  ${(accuracy * 100).toFixed(1)}%`,
+            '',
+            '  Per-Signal Breakdown:',
+            ...Object.entries(signalAccuracy).sort().map(([id, s]) => {
+                const p = s.tp / Math.max(s.tp + s.fp, 1);
+                const r = s.tp / Math.max(s.tp + s.fn, 1);
+                return `    ${id.padEnd(22)} TP:${String(s.tp).padStart(3)} FP:${String(s.fp).padStart(3)} FN:${String(s.fn).padStart(3)}  precision:${(p * 100).toFixed(0).padStart(4)}%  recall:${(r * 100).toFixed(0).padStart(4)}%`;
+            }),
+        ];
+        if (falsePositives.length > 0) {
+            report.push('', '  False Positives (durable content incorrectly warned):');
+            report.push(...falsePositives);
+        }
+        if (falseNegatives.length > 0) {
+            report.push('', '  False Negatives (ephemeral content missed):');
+            report.push(...falseNegatives);
+        }
+        report.push('═══════════════════════════════════════════════════════════\n');
+        console.log(report.join('\n'));
+        // Assertions — set minimum acceptable thresholds
+        // Precision must stay very high (false positives erode trust)
+        assert.ok(precision >= 0.95, `Precision ${(precision * 100).toFixed(1)}% below 95% minimum`);
+        // Recall baseline: regex catches ~56% on the full 415-case adversarial set.
+        // TF-IDF classifier is expected to improve this. Threshold is a regression guard.
+        assert.ok(recall >= 0.50, `Recall ${(recall * 100).toFixed(1)}% below 50% minimum`);
+        assert.ok(accuracy >= 0.70, `Accuracy ${(accuracy * 100).toFixed(1)}% below 70% minimum`);
+    });
+});