Lore framing markers and project knowledge catalog IDs

Lore framing notes must retain their protocol-significant leading marker. Knowledge-delta notes start with the exact stable prefix "[Lore knowledge update —" because parsing, cache assertions, and legacy migration matching depend on startsWith(). Reserve bracketed Lore system markers for system blocks; never place them in tool descriptions. Project catalogs must state that Lore knows what project knowledge exists and can recall it, preserve full canonical k:/xk: IDs for exact ltm.get(id) lookup, and never advertise tombstoned entries.