tune-temperature-policylisted

# Tune the temperature policy remindb's temperature system has five knobs in `pkg/temperature/config.go`. They're tightly coupled — changing one shifts the behavior of search ranking, the cold-set query, and the client-facing notification stream. Tuning is rarely a one-file change. The skill exists because two public skills document this policy for agents: - `skills/remind/SKILL.md` — owns the **numerics** in the mental model (decay rate, access boost, cold/notify thresholds, tick interval, ranking score formula, notification payload shape). These stay in the SKILL.md router, not a reference. - `skills/memorize/references/lifecycle.md` — owns the **summarization workflow** the notification triggers (`MemoryFetch` → `MemorySummarize`). The `memorize` SKILL.md router only points at it. If the numbers or the workflow drift from the code, agents will reason from stale defaults. ## What the knobs do | Knob | Default | Affects | |---|---|---| | `DecayRate` | `0.05` | `decayFactor = exp(-rate × elapsed_hours)` — applied each tick to every node | | `AccessBoost` | `0.15` | Added to a node's temperature on read; capped at `1.0` by SQL `min(1.0, …)` | | `ColdThreshold` | `0.1` | Below this, nodes are "cold" — used by `GetColdNodes` and the search relevance floor (`score = relevance × (0.3 + 0.7 × temperature) × recency`) | | `NotifyThreshold` | `0.1` | Below this, the server pushes an MCP notification (`level: "warning"`, `logger: "remindb.temperature"`) — gated by per-node hyste