After the initial call and one retry both return empty content,
vision_tools.py was returning {"success": true, "analysis": "There was
a problem..."}.  Callers that branch on success would treat this as a
valid analysis.

Return {"success": false, "error": "..."} instead, consistent with
how all other failure paths in the same function behave.

…g_tool

Both tools passed the full os.environ (including all provider API keys
and tokens) to child processes via {**os.environ}.  A crashing subprocess
or one that logs its environment would expose every secret in the session.

The existing _sanitize_subprocess_env() helper in tools/environments/local.py
(with its 130+ var blocklist) was already used by LocalEnvironment and
process_registry but not by these two tools.  This fix extends it to:

  - tools/browser_tool.py     browser_env = {**os.environ}
  - tools/rl_training_tool.py env={**os.environ, 'TINKER_API_KEY': ...}

The sanitizer blocklist targets terminal subprocesses (e.g. codex CLI) so
it strips credentials these tools legitimately need.  Re-allow the minimum
required set via the _HERMES_FORCE_ prefix:

  - browser_tool:  BROWSERBASE_API_KEY, BROWSERBASE_PROJECT_ID,
                   BROWSER_USE_API_KEY, FIRECRAWL_API_KEY,
                   FIRECRAWL_API_URL, FIRECRAWL_BROWSER_TTL
  - rl_training:   TINKER_API_KEY, WANDB_API_KEY

Provider keys (OPENAI_API_KEY, ANTHROPIC_TOKEN, GOOGLE_API_KEY, etc.) are
now blocked as intended.

Related: NousResearch#3628 (broader env-scoping feature)

Adds plugins/memory/mnemoria/ with MnemoriaMemoryProvider — a MemoryProvider
adapter backed by the mnemoria PyPI package (mnemoria>=0.1.0).

- plugin.yaml declares pip_dependencies so hermes memory setup auto-installs
- provider.py imports from mnemoria.* (not the old unified_memory module)
- pyproject.toml gains [mnemoria] optional extra

Enable with: pip install 'hermes-agent[mnemoria]'
Then set memory.provider: mnemoria in ~/.hermes/config.yaml

When /background was sent during an active run, it was not in the
platform adapter's bypass list and fell through to the interrupt path
instead of spawning a parallel background task.

Add "background" to the active-session command bypass in the platform
adapter, and add an early return in the gateway runner's running-agent
guard to route /background to _handle_background_command() before it
reaches the default interrupt logic.

Fixes NousResearch#6827

Adds a regression test verifying that /background bypasses the
active-session guard in the platform adapter, matching the existing
test pattern for /stop, /new, /approve, /deny, and /status.