Catalog-defined ACP agents never receive HAPPIER_SESSION_ID #630

Summary

Agents built on createCatalogDefinedAcpEntry (agy/Antigravity, Devin, Kimi, and other catalog ACP agents) never get HAPPIER_SESSION_ID in their process environment, unlike Claude, Codex, Copilot, Cursor, Auggie, Kilo, and Gemini.

Impact

Nested Happier CLI actions (for example happier session create) treat the caller as cli-global, so equal-mode requests fail with permission_escalation_denied. Agents also cannot resolve their own session or title. This is the same class of bug #310 fixed for Codex, but the catalog ACP path still drops processEnv.

Repro (observed on CLI 0.2.16)

1. Start a Happier agy session.
2. Inspect the agy_acp_server process environment → no HAPPIER_SESSION_ID.
3. Compare with Copilot → HAPPIER_SESSION_ID is present.

Root cause

runStandardAcpProvider already passes processEnv: withCurrentHappierSessionId(...).
runCatalogDefinedAcpAgent's createRuntime did not destructure or forward processEnv into createCatalogProviderAcpRuntime (which already accepts it and maps it to the backend env).

Related

• fix(cli): preserve nested session permission authority #310