tnyma-bridge 0.1.0

package/README.md

@@ -0,0 +1,35 @@
+# tnyma-bridge
+
+Tnyma Bridge connects your local OpenClaw app to Tnyma.
+
+## Install
+
+```bash
+npm i -g tnyma-bridge
+```
+
+Requires Node.js 20 or newer.
+
+## Use
+
+The bridge starts automatically after global install.
+
+Open the local binding page:
+
+```text
+http://127.0.0.1:18788
+```
+
+The page shows the QR code and pairing code. Scan the QR code or enter the pairing code in Tnyma to bind this computer.
+
+Keep the process running while you want this computer connected.
+
+## Troubleshooting
+
+If OpenClaw is not detected, start OpenClaw first and then restart `tnyma-bridge`.
+
+If the bridge is not running, start it manually:
+
+```bash
+tnyma-bridge
+```

package/bundle/feishu-bot-creator/README.md

@@ -0,0 +1,66 @@
+# feishu-bot-creator
+
+Headless-Playwright script that bridge-node spawns to automate the
+Feishu / Lark open-platform "create custom-built bot" flow.
+
+## How it fits
+
+```
+[Browser] → /v1/integrations/feishu/bind/stream (SSE)
+   │
+   ▼
+[bridge-node] handlers/integrations-feishu.ts
+   │              └── integrations/feishu/bind-session.ts (spawn + line-buffered SSE)
+   ▼
+[python3 feishu_bot_creator.py create --platform feishu]
+   │
+   ▼
+Feishu open platform (QR scan, internal /developers/v1 APIs)
+   │
+   ▼
+Writes channels.feishu.accounts.<id>.{appId, appSecret, ...}
+into $FEISHU_BOT_OPENCLAW_CONFIG (default /root/.openclaw/openclaw.json)
+```
+
+The script emits one JSON line per event on stdout. bind-session.ts parses
+each line, strips `app_secret` from `finish` events and credential-log
+lines, then re-emits as SSE so neither the browser nor the cloud
+control-plane ever sees the raw secret.
+
+## Standalone usage (manual debugging on the VM)
+
+```bash
+# Install Python deps + Chromium (one-time per VM/image)
+python3 feishu_bot_creator.py init
+
+# Run the full flow. Each JSON line is one event.
+python3 feishu_bot_creator.py create --platform feishu
+
+# Kill leftover Chromium / clear profile lock files
+python3 feishu_bot_creator.py cleanup
+```
+
+## Environment knobs
+
+| Var | Default | Notes |
+|---|---|---|
+| `FEISHU_BOT_CDP_PORT` | `9222` | Chromium remote-debugging port |
+| `FEISHU_BOT_STATE_DIR` | `/tmp` | Profile dir + cached avatar + state file land here |
+| `FEISHU_BOT_OPENCLAW_CONFIG` | `/root/.openclaw/openclaw.json` | Where channels.feishu.* gets written |
+| `FEISHU_BOT_OPENCLAW_ALLOW_FROM` | `/root/.openclaw/credentials/feishu-default-allowFrom.json` | Owner open_id allowlist |
+| `FEISHU_BOT_ACCOUNT_ID` | `default` | `channels.feishu.accounts.<id>` key |
+| `FEISHU_BOT_SCRIPT_PATH` | (resolved relative to bind-session.js) | Override when running from an unusual layout |
+| `FEISHU_BOT_PYTHON_BIN` | `python3` | Path to the Python interpreter |
+
+## Concurrency
+
+The script hard-codes one CDP port and one profile dir, so only one
+session can run on a bridge at a time. bind-session.ts enforces this with
+a process-level lock; concurrent starts return `409 conflict_session_busy`.
+
+## Image dependencies
+
+`docker/bridge-node.Dockerfile` installs `python3 + playwright +
+chromium` in the final stage so the script is ready to run on container
+start with no first-request latency. See that file for the full apt /
+pip / playwright install sequence.