Add Android node foundation with FCM push support

This commit is contained in:
William Valentin
2026-02-16 12:55:22 -08:00
parent 58c4b0b9bb
commit a954d7e136
11 changed files with 190 additions and 19 deletions
+3 -5
View File
@@ -669,7 +669,7 @@ Publish companion/node runtime status metadata (for example macOS menu-bar heart
#### `node.push_token.set`
Register a node push token (currently APNs) for companion delivery routing.
Register a node push token (APNs or FCM) for companion delivery routing.
Requires `server.nodes.push.enabled: true`.
**Request:**
@@ -678,10 +678,8 @@ Requires `server.nodes.push.enabled: true`.
"id": 13,
"method": "node.push_token.set",
"params": {
"provider": "apns",
"token": "abcd1234abcd1234abcd1234abcd1234",
"topic": "com.example.flynn",
"environment": "sandbox"
"provider": "fcm",
"token": "fcm_abcdefghijklmnopqrstuvwxyz123456"
}
}
```
@@ -0,0 +1,44 @@
# Android Node Foundation Checklist
**Date:** 2026-02-16
**Scope:** Close OpenClaw "Android node" gap with Android push-ready companion support.
## Goal
Extend companion-node push registration beyond iOS so Android nodes can register FCM tokens with the same safety model and operator visibility.
## Implemented
- Extended node push token protocol:
- `node.push_token.set` now accepts `provider: "apns" | "fcm"`.
- Added Android/FCM support in node handler runtime:
- store provider-specific push metadata in connection state.
- `fcm` tokens are accepted without APNs environment/topic requirements.
- Preserved secret safety:
- `system.nodes` continues exposing only masked `tokenPreview`.
- Kept policy model consistent:
- still gated by `server.nodes.push.enabled`.
- role scopes unchanged (companion-only write path).
## Tests
- `src/gateway/protocol.test.ts`
- Added valid FCM parse coverage.
- `src/gateway/handlers/node.test.ts`
- Added FCM push-token registration test for Android companion.
- `src/gateway/server.test.ts`
- Added end-to-end Android node + `node.push_token.set` + `system.nodes` verification.
- Existing auth/config/system tests continue passing.
## Docs Updated
- `README.md` node method notes now mention APNs + FCM.
- `docs/api/PROTOCOL.md` now documents APNs/FCM provider support for `node.push_token.set`.
## Validation Run
```bash
pnpm test:run src/gateway/protocol.test.ts src/gateway/handlers/node.test.ts src/gateway/server.test.ts src/gateway/auth.test.ts src/gateway/handlers/handlers.test.ts src/config/schema.test.ts
pnpm typecheck
pnpm build
```
+25 -3
View File
@@ -572,6 +572,28 @@
],
"test_status": "pnpm test:run src/gateway/protocol.test.ts src/gateway/auth.test.ts src/gateway/handlers/node.test.ts src/gateway/handlers/handlers.test.ts src/gateway/server.test.ts src/config/schema.test.ts + pnpm typecheck + pnpm build passing"
},
"android-node-foundation": {
"file": "2026-02-16-android-node-foundation-checklist.md",
"status": "completed",
"date": "2026-02-16",
"updated": "2026-02-16",
"summary": "Implemented Android node companion foundation by extending `node.push_token.set` to accept FCM tokens in addition to APNs, with masked operator visibility in `system.nodes` and existing node push policy/scope controls preserved.",
"files_created": [
"docs/plans/2026-02-16-android-node-foundation-checklist.md"
],
"files_modified": [
"src/gateway/protocol.ts",
"src/gateway/protocol.test.ts",
"src/gateway/handlers/node.ts",
"src/gateway/handlers/node.test.ts",
"src/gateway/handlers/system.ts",
"src/gateway/server.ts",
"src/gateway/server.test.ts",
"README.md",
"docs/api/PROTOCOL.md"
],
"test_status": "pnpm test:run src/gateway/protocol.test.ts src/gateway/handlers/node.test.ts src/gateway/server.test.ts src/gateway/auth.test.ts src/gateway/handlers/handlers.test.ts src/config/schema.test.ts + pnpm typecheck + pnpm build passing"
},
"qmd-backend": {
"file": "2026-02-16-qmd-backend-checklist.md",
"status": "completed",
@@ -3133,7 +3155,7 @@
}
},
"overall_progress": {
"total_test_count": 1792,
"total_test_count": 1795,
"all_tests_passing": true,
"p0_completion": "3/3 (100%)",
"p1_completion": "4/4 (100%)",
@@ -3148,12 +3170,12 @@
"tier2_completion": "4/4 (100%) — inbound webhooks, vector memory search, Dockerfile, heartbeat monitor",
"tier3_completion": "5/5 (100%) — lane queue, credential redaction, web UI token dashboard, xAI (Grok) provider, Voyage AI embeddings",
"tier4_completion": "4/4 (100%) — gateway lock, shell completion, Tailscale Serve/Funnel, DM pairing codes",
"feature_gap_scorecard": "122/128 match (95%), 0 partial (0%), 6 missing (5%)",
"feature_gap_scorecard": "123/128 match (96%), 0 partial (0%), 5 missing (4%)",
"operator_dx_milestone": "Phase 3 (Live Ops Dashboard): 2/2 plans complete — milestone done",
"gmail_auth_cli": "flynn gmail-auth command implemented with OAuth2 flow, doctor check, config routed to Telegram",
"native_audio_support": "completed — smart routing for native audio (Gemini/OpenAI/GitHub) vs Whisper transcription fallback",
"remaining_phases_completion": "Phase 1: 3/3 (100%) — context levels, command registry, memory structure. Phase 2: 3/3 (100%) — component registry, confidence routing, history index. Phase 3: 2/2 (100%) — adaptive memory/compaction, truthfulness/autonomy hardening",
"next_up": "OpenClaw gap: Android node (open next scoped implementation checklist)"
"next_up": "OpenClaw gap: LINE/Feishu/Zalo channel adapter set (open next scoped implementation checklist)"
},
"soul_md_and_cron_create": {
"date": "2026-02-11",