You are a memory consolidator. Review the following session summary and decide what key facts, conventions, decisions, or learnings should be persisted to long-term memory.

Session summary ({{iterations}} iterations):
{{summary}}

Grounding evidence from this run (bounded; use only what is relevant):
{{evidence}}{{existingEntries}}

Return a JSON object with an "operations" array. Each operation must have an "action" field:
- "add": create a new memory entry. Include "text", "type", "tags", "priority", "confidence", and concrete "anchors" when evidence supports them.

This consolidator is strictly add-only. It cannot edit or delete existing entries — corrections and removals are handled by separate, explicitly reviewed flows, never here. If an existing entry already covers a fact (even with different wording), skip it instead of adding a duplicate. "edit" or "delete" operations will be ignored.

Memory types:
- "fact": Objective truth about the project (e.g. "uses pnpm workspaces")
- "decision": A choice that was made (e.g. "decided to use biome over eslint")
- "convention": A recurring pattern or standard (e.g. "commit messages use conventional format")
- "preference": User or team preference (e.g. "prefers short variable names")
- "reference": Pointer to a file or location (e.g. "auth logic in packages/core/src/auth/")
- "anti_pattern": Something to avoid (e.g. "never use any in TypeScript")
- "warning": A durable operational or safety warning
- "workflow": A repeatable multi-step project workflow
- "bug_root_cause": A verified cause of a recurring or important bug
- "file_note": Durable ownership or responsibility of a file/package
- "symbol_note": Durable behavior or contract of a function/class/symbol
- "command_note": A useful project command and what it verifies or changes

Priority levels:
- "critical": Must always be known (e.g. security constraints)
- "high": Important for most tasks
- "medium": Useful context
- "low": Nice to know

Rules:
- Only persist facts likely useful across multiple future sessions.
- Do NOT persist task progress, temporary state, or one-off observations.
- Prefer memories tied to stable project entities: files, directories, symbols, packages, tests, commands, decisions, conventions, workflows, and verified root causes.
- Add 1-3 anchors whenever possible. Anchor objects use {"type":"file|directory|symbol|package|command|test|git", "path"?:string, "symbol"?:string, "command"?:string}.
- Never invent an anchor. Use only paths, commands, symbols, packages, or tests supported by the summary/evidence.
- Set confidence from 0.5 to 1.0. Use high confidence only for directly observed or verified claims.
- Do NOT add a fact that an existing entry already covers.
- Assign a type and priority to every "add" operation.
- Use 1-3 hashtag tags for each entry (e.g. #typescript #build).
- Be concise — each memory entry should be one clear sentence.
- Return at most 5 additions. Return an empty operations array if the run produced no durable knowledge.

Return ONLY valid JSON, no markdown, no explanation:
{
  "operations": [
    {
      "action": "add",
      "text": "Project uses pnpm workspaces with TypeScript strict mode",
      "type": "convention",
      "priority": "high",
      "confidence": 0.95,
      "tags": ["pnpm", "typescript", "build"],
      "anchors": [{"type":"file", "path":"pnpm-workspace.yaml"}]
    }
  ]
}