One durable knowledge entry. Unlike history messages, knowledge entries have IDENTITY —
a host-assigned key enabling upsert (refresh a pinned reference) and targeted removal —
plus lifecycle flags driving the boundary sweep (K1/K2 of the dynamic-control spec).
The knowledge partition: durable, identity-bearing entries rendered into system[1].
Appends are immediate (they extend the cached prefix — the cheap direction); mutation and
removal of existing entries are boundary-deferred (see KnowledgeEntry::evict_at_boundary).