mistakeslisted

# engram mistakes Surface bi-temporal mistake memory from engram's graph. Each mistake has a `valid_until` timestamp and an `invalidated_by_commit` reference, so an old mistake auto-expires when its underlying cause is fixed. Run: ``` engram mistakes -p $CLAUDE_PROJECT_DIR ``` The output lists active (still-valid) mistakes with confidence scores. When a mistake matches a query, engram surfaces it with ⚠️ at the top of the context packet, weighted 2.5× to ensure it gets attention. Use this skill: - Before refactoring a module: "are there known sharp edges here?" - During debugging: "has this kind of error been seen before?" - When onboarding to a new area of the codebase: "what's broken or fragile?" To record a new mistake explicitly: ``` engram learn "Don't pass options.scope=user; SETTINGS_LOCAL takes precedence." -p $CLAUDE_PROJECT_DIR ``` ## Example invocations **User:** "I'm about to refactor the rate limiter — anything I should know?" **You:** Run `engram mistakes -p $CLAUDE_PROJECT_DIR`. Filter mentally for entries related to "rate", "limit", "mutex", or the file paths the user mentions. Surface the matches with their confidence scores: "engram has 3 active mistakes near this code, and one of them flagged this exact module:" **User:** "Why does this test keep flaking?" **You:** Run `engram mistakes -p $CLAUDE_PROJECT_DIR`. Look for entries about flakiness, timing, race conditions, or the test file's name. If a related mistake exists, quote it verbatim — chanc