feat: v0.4 resilience release

README.md

@@ -107,15 +107,23 @@ Your `agy` agent reads these when running the deploy prompt. You set them when i
 
 | Variable | Default | Description |
 |---|---|---|
-| `AGENT_UID` | `AgyBridge` | WuKongIM subscription identity |
-| `AGENT_TOKEN` | *(empty)* | WuKongIM auth token (supply yours) |
-| `WUKONG_WS_URL` | `ws://localhost:5200` | WK WebSocket URL |
-| `WUKONG_API_URL` | `http://localhost:5001` | WK REST API base |
-| `SIDECAR_URL` | `http://localhost:5400` | WK sidecar for message routing |
+| `AGENT_UID` | `AgyBridge` | WuKongIM subscription identity (supports `APEX_AGENT_UID` fallback) |
+| `AGENT_TOKEN` | *(empty)* | WuKongIM auth token (supports `APEX_AGENT_TOKEN` fallback) |
+| `WUKONG_WS_URL` | `ws://localhost:5200` | WK WebSocket URL (supports `APEX_WUKONG_WS_URL` fallback) |
+| `WUKONG_API_URL` | `http://localhost:5001` | WK REST API base (supports `APEX_WUKONG_API_URL` fallback) |
+| `SIDECAR_URL` | `http://localhost:5400` | WK sidecar for message routing (supports `APEX_SIDECAR_URL` fallback) |
 | `STATE_DIR` | `~/.aios-mcp-state` | DSD state file location |
 | `PID_FILE` | `/tmp/agy-bridge-<UID>.pid` | Singleton lock file |
 | `LIFE_LOG_FILE` | `/tmp/antigravity-bridge-<UID>.log` | Lifecycle event log |
 | `AGY_PRIMARY_CASCADE_ID` | *(empty)* | Override DSD with an explicit session ID |
+| `WK_PROXY_URL` | *(empty)* | WuKongIM proxy server URL |
+| `WK_PROXY_TOKEN` | *(empty)* | WuKongIM proxy authorization token |
+| `AGY_WORKSPACE` | *(empty)* | Workspace directory path hint (falls back to `AIOS_WORKSPACE`) |
+| `AGY_WAKE_ON_ALL` | `0` | Set to `1` to bypass wake-word filtering and process all room messages |
+| `AGY_DIRECT_MCP_FALLBACK` | `1` | Enable/disable direct REST-based MCP fallback (set to `0` to disable) |
+| `AGY_WAKE_FILTER_FILE` | *(auto-generated)* | Custom JSON file path for wake-filtering state |
+| `APEX_WAKE_MENTIONS` | *(empty)* | Comma-separated list of additional wake words beyond `AGENT_UID` |
+| `AGY_SUBSCRIBE_ROOMS` | *(empty)* | Comma-separated list of room IDs to auto-subscribe to on startup |
 | `TELEGRAM_BOT_TOKEN` | *(empty)* | (Telegram sample only) bot token from @BotFather |
 
 ## Samples
@@ -166,9 +174,9 @@ We mention this because **the shape of the iteration is itself a signal**: three
 
 ## Known Limitations
 
-This is a v0.3 reference implementation, not production-hardened software:
+This is a v0.4 resilience-focused reference implementation:
 
-- **Not yet integration-tested end-to-end in its final form.** The DSD pattern and the WK JSON-RPC subscription logic have each been validated in earlier iterations and code-reviewed independently, but the final `bridge.ts` (which combines them) has not been run as a single integrated process against a live Antigravity CLI + WuKongIM server. v0.4 priority.
+- **Environment-resolution caveats.** v0.4 integrates and composition-tests the resilience features (Dynamic Session Discovery, state catch-up, wake-filtering, REST direct MCP fallback, and auto-subscriptions) used internally inside Apex Learn's aiOS substrate. However, first-time external deployments in clean environments have not been fully integration-tested; first-time external users may surface environment-resolution edge cases. Please file issues.
 - **Single-host assumption.** The DSD state file is local. Multi-host fan-out is unsolved here.
 - **No authn/authz on the bridge process.** Anyone with local read access to the state file can target the active session. Treat the bridge process as in-trust.
 - **WK token in plaintext env.** `AGENT_TOKEN` is read from process env. For production, use a secrets manager.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "antigravity-bridge",
-  "version": "0.2.0",
+  "version": "0.4.0",
   "description": "Lightweight message bridge connecting WuKongIM chat substrate to the Antigravity CLI via Dynamic Session Discovery (DSD).",
   "type": "module",
   "scripts": {