v1.1.0

Search now knows what kind of secret it found.

If you have three credentials named "github" — an SSH key, an API token, and a login — asking for "github" used to hand you a list of names and make you guess. Now the vault labels ambiguous matches by entry type, and the CLI can narrow the search up front.

Vault (1.1.9)

• Search accepts a type narrower, so ambiguous queries can be scoped to one entry type instead of listing everything that matches the name.
• Ambiguous replies now carry the entry type alongside the name — no more matching by name alone.
• Every administrative action on a vault now needs its own authorization over the encrypted control channel. Reads and writes of your credentials are untouched — this closes off the control surface, not the data plane.
• Vaults can raise real-time alerts to fleet operators over the same secure channel.

CLI (1.2.1)

• clavitor-cli get <query> --type <entry type> narrows a search by type. Short aliases work too — api for api_key, ssh for ssh_key.
• At a terminal, ambiguous matches now show the type next to the name. (Agent/scripted callers stay count-only by design — no behavior change there.)

Proxy (1.2.1)

• Rebuilt against the updated shared client to speak the new ambiguity format. No behavior change.

Platform

• Translated pages now publish from a single artifact pushed to both our data centers — what you see in another language always matches what we shipped, everywhere.
• Outages are now confirmed by a second, independent watchtower before we call them — fewer false alarms, faster real response.

No breaking changes. Existing installs keep working unchanged; grab 1.2.1 from clavitor.ai/downloads when you want the new flags.