organic-os v0.5.1 - inline approval buttons, and knowing whether your update landed

Two things: a Telegram UX upgrade that was already on main, and tooling so an update that does not take is visible instead of silent.

• Inline Approve/Reject buttons in Telegram. Approving no longer means typing 'approve ' - the proposal arrives as a readable message (title, framing, a reasoning excerpt) with tap-to-approve and tap-to-reject buttons. Over-long ids fall back to the typed grammar rather than shipping a button that cannot resolve, the redaction advisory is applied to the rendered text, and the typed and reply-context grammars still work unchanged.
• /organic-os:diagnose now reports update currency. It reads the version you are running and the latest published version, and tells you plainly whether you are current, behind, or ahead - with correct semver ordering, so 0.5.10 is newer than 0.5.9. This is an on-demand read of an already-public version number, not telemetry: nothing about you is sent, and the diagnostic itself is never transmitted.
• A troubleshooting section for the update that reports success but does not change the running version. This is a Claude Code and Cowork plugin-manager behavior, not something a plugin can fix from inside its own update - the honest remedy is a clean reinstall (CLI) or remove-and-re-add (Cowork), which loses nothing because your brain and config live outside the plugin. Worth a /bug to the Claude Code team.
• release-check, a maintainer step that fails when plugin code has changed since the last tag but the version was not bumped. That exact gap is why the inline-buttons work sat on main invisible to the updater under an unchanged 0.5.0 - the updater compares version numbers, so new code only reaches users when the number moves.

415 tests, 9 audit checks, 8 gate probes, CI green.