update readme

Author: silesky

packages/signals/signals-runtime/README.md

@@ -1,10 +1,54 @@
 # @segment/analytics-signals-runtime
 Encapsulates Signals runtime functionality, in order to share logic between the signals plugins for browser and mobile.
 
+### Installation
+```bash
+# npm
+npm install @segment/analytics-signals-runtime
+# yarn
+yarn add @segment/analytics-signals-runtime
+# pnpm
+pnpm install @segment/analytics-signals-runtime
+```
+
+### Usage
+
+### As a regular library
+
+```ts
+import { 
+  WebSignalsRuntime,
+  // WebRuntimeConstants,
+  // MobileSignalsRuntime
+  // MobileRuntimeConstants
+} from  '@segment/analytics-signals-runtime'
+
+const signals = new WebSignalsRuntime([....])
+
+// get the more recent network signal in the buffer
+const networkSignal = signals.find(null, 'network')
+
+// all signals
+const allInstrumentationSignals = signals.find(null, 'network')
+
+
+```
+### As a string
+Exposes the SignalsObject
+
+```ts
+import { getRuntimeCode } from '@segment/analytics-signals-runtime``
+
+eval(`
+ ${getRuntimeCode()}
+ signals.signalBuffer = [....]
+ `)
+
+```
 ### Development
 `yarn build` generate the following artifacts:
 | Generated File(s) | Description | 
 |--------|-------------|
 | `/dist/runtime/index.[platform].js`, `/[platform]/get-runtime-code.generated.js` | Exposes `globalThis.Signals` and constants (e.g. `SignalType`), either through the script tag or in the mobile JS engine | 
 | `/dist/editor/[platform]-editor.d.ts.txt` | Type definitions for monaco editor on app.segment.com 
-| `/dist/esm/index.js` | Entry point for `@segment/analytics-signals` and the segment app, for consumers that want to consume the types / runtime code as an npm package. | 
+| `/dist/esm/index.js` | Entry point for `@segment/analytics-signals` and the segment app, for consumers that want to consume the types / runtime code as an npm package. |