0.35.4: Telegram Session Thread Continuity

• Telegram pin: Advances only the exact Telegram pin from 0.57.2 to 0.57.3. A session replaced inside one Pi process now reuses its preserved Thread on every registration path instead of provisioning a second tab, and a new session registering in a folder whose previous session is provably gone adopts that binding's exact target and slot while the predecessor binding is re-keyed. A live predecessor or an ambiguous candidate set keeps ordinary provisioning.
• Checks: The exact-pin test, README inventory and pointer targets now read 0.57.3; the seven published pointer entrypoints and declared Skill paths are unchanged. Packed validation covers build, types, tests, audit and bundle inventory only, so installed-client behavior remains an operator check in Backlog.