FR: Allow Environments to reference Vault Items

Description: Currently, 1Password Environments and Vault Items are two completely separate systems with no connection between them. This creates a fundamental problem for professional workflows:

•  Environments provide fast, secure secret delivery via Named Pipes – great for local development
• Vault Items provide rotation, audit trails, access control, and CLI management – great for operations

But you have to choose one or maintain both in parallel, which means either giving up rotation or giving up fast secret delivery.

Proposed Solution: Allow an Environment variable to be linked to a Vault Item. The Environment would act as a structured view over Vault Items, not a separate data store.

Benefits:

• Single source of truth – secrets live in Vault Items, Environments just expose them
• Rotation works automatically – rotate the Vault Item, the Environment reflects the change immediately
• Audit trail remains intact – all access and changes tracked in Vault Items
• Named Pipe delivery stays fast – no change to the developer experience