@floomhq/signaldash 0.39.5 → 0.39.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +7 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -120,7 +120,7 @@ setup installs both from the same pinned npm package
|
|
|
120
120
|
the human chose to execute:
|
|
121
121
|
|
|
122
122
|
```bash
|
|
123
|
-
npx -y @floomhq/signaldash@0.39.
|
|
123
|
+
npx -y @floomhq/signaldash@0.39.6 <invite-code>
|
|
124
124
|
```
|
|
125
125
|
|
|
126
126
|
Run that command in a terminal, not in an agent chat. Do not ask an agent to
|
|
@@ -389,6 +389,12 @@ linkedin.com to fill the gap. An empty item list therefore means only that the
|
|
|
389
389
|
visible SignalDash and Buffer sources are empty, never that the native LinkedIn
|
|
390
390
|
calendar is empty.
|
|
391
391
|
|
|
392
|
+
The read-only calendar page renders each stored SignalDash image through a
|
|
393
|
+
calendar-session-protected, tenant-scoped media route. It does not invent
|
|
394
|
+
visuals for Buffer entries because SignalDash does not store their media bytes.
|
|
395
|
+
Calendar media is no-store and becomes unavailable when the session expires or
|
|
396
|
+
the originating user is revoked.
|
|
397
|
+
|
|
392
398
|
`li_scheduled_post_preview` returns a short-lived, single-use browser handoff
|
|
393
399
|
for one exact active SignalDash post owned by the authenticated user. The page
|
|
394
400
|
shows only that post, including its stored image attachments. Preview sessions
|