Environments: .env re-import duplicates keys on stable, and focusing a multiline value strips its newlines on save

I'd like to report two bugs in 1Password Environments (beta). Both cause the stored data to differ from what was entered, so we've put moving our CI secrets to Environments on hold for now.

Setup: Business account, 1Password for Mac 8.12.42 (81242036), stable channel.

I've also reported this through the support chat on support.1password.com (in Japanese), which forwarded it to the support team by email. I'm posting here so the product team can see it directly.

Bug 1: Re-importing a .env file duplicates existing keys

Steps to reproduce:

1. Import a .env file into an Environment (e.g. `FOO=old`).
2. Import another .env file into the same Environment where only the value changed (e.g. `FOO=new`).

Expected: The existing `FOO` is updated to `new`.

Actual: No prompt appears. A new `FOO` entry is added, so the Environment now lists `FOO` twice.

The beta release notes for 8.11.20 say "If duplicates are detected when you import environment variables, you can now choose to ignore, overwrite, or keep both," but I can't find this in the stable release notes, and 8.12.42 (stable) doesn't show the choice.

Impact: `op run --environment` uses the entry that was added last, but the app doesn't show which one is in effect, and the old value is never removed.

Bug 2: A multiline value loses its newlines when the field is focused and saved

Background: Multiline values (e.g. private keys) can't be entered with "New variable" in the app; the only way to add one is .env import.

Steps to reproduce:

1. Add a multiline value via .env import.
2. In the desktop app, click into (focus) that value's field.
3. Save without changing anything.

Expected: The value keeps its newlines.

Actual: The value is saved with all newlines removed.

Impact: Just focusing the field corrupts values such as private keys, even though nothing was edited.

Requests

• Ship the ignore / overwrite / keep both choice on import to the stable channel. When is it planned?
• Allow entering and editing multiline values in the app. At minimum, don't strip newlines when a field is only focused.
• Support importing a .env file into an Environment from the CLI (e.g. `op environment import`). Today the CLI can only read Environments (`op run --environment`), so every update has to go through the desktop app, which is where both bugs above bite. A CLI import would let us script updates, preserve multiline values, and review changes in code.

Are there any workarounds for these two issues, and is a fix planned?