Phase 1: real vault and plugin loading

Append-only.

UNIXUSAT=1792985975299 · commit a117020

The author’s second orders, word for word:

### Q6
start from Bitwarden / Vaultwarden
but each of mentioned add in separed script file in 
- `src/amoorion/vault/http_vault.py` - HashiCorp Vault / OpenBao, KV
- `src/amoorion/vault/bw_cli.py` -  Bitwarden / Vaultwarden through the `bw` CLI
- `src/amoorion/vault/kpxc_db_file.py` - KeePassXC database file
- `src/amoorion/vault/default.py` - for .env setup 

### Q7
with Python entry points
separate package, and one shared interface

### Q8
yep````

The questions they answer, with their decisions:

### Q6: which vault

Secrets come from a vault (Q3). Which one does amoorion talk to first?

- HashiCorp Vault / OpenBao, KV v2 over HTTP (`requests` is already a
  dependency; a token or AppRole in `.env` establishes the link)
- Bitwarden / Vaultwarden through the `bw` CLI (client-side decryption, so
  no plain HTTP API)
- KeePassXC database file

*Lean:* OpenBao / HashiCorp Vault KV v2 first; the backend sits behind
`amoorion.vault.base.Vault`, so others can follow.

**Decision:** Bitwarden / Vaultwarden first, and every one of them, each in
its own file: `vault/http_vault.py` (HashiCorp Vault / OpenBao KV),
`vault/bw_cli.py` (Bitwarden / Vaultwarden through `bw`),
`vault/kpxc_db_file.py` (KeePassXC database file), `vault/default.py` (the
`.env` setup).

### Q7: per-platform plugins "with …"

The answer to Q2 ends in "adopt per-platform plugins with". With what?

*Lean:* with Python entry points (group `amoorion.plugins`), so a platform
can live in this repository (`src/amoorion/plugins/<platform>/`) or as a
separate package, and one shared interface (`post`, `read`, `reply`).

**Decision:** Python entry points; a plugin can be a separate package; one
shared interface.

### Q8: `dotenv` package

`pyproject.toml` has `dotenv`, a shim that only installs `python-dotenv`.
Depend on `python-dotenv` directly?

*Lean:* yes.

**Decision:** yes.

## UNIXUSAT=1792986372873 · commit 2da4908

The orders carried out. The author's `help` task made runnable.
`python-dotenv` replaces the shim (Q8). The vault split into one module per
backend (Q6): `bw_cli.py` (Bitwarden / Vaultwarden, the first), `http_vault.py`
(HashiCorp Vault / OpenBao KV v2), `kpxc_db_file.py` (KeePassXC, extra
`keepassxc`), `default.py` (the `.env` setup); the link gained
`AMOORION_VAULT_PATH`. Plugins come through the `amoorion.plugins` entry
points (Q7), guide in `docs/plugins.md`. New methods `accounts` and
`reply`. Phase 2 began with the Bluesky plugin. Q9–Q10 opened.