@drawbridge/drawbridge-agents 0.1.17 → 0.1.19
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.
|
@@ -24,7 +24,10 @@ need to retest. Use this right after merging the work to `develop` (which deploy
|
|
|
24
24
|
3. **Draft the comment.** A concise summary of what changed (not a changelog dump), then an
|
|
25
25
|
explicit **Retest & verify** section: the exact steps and expected results to confirm the
|
|
26
26
|
fix, and any data/setup needed. Ground the retest steps in the actual behaviour that
|
|
27
|
-
changed.
|
|
27
|
+
changed. **Open the comment with an @-mention of the reassignee** — use `html_text` and
|
|
28
|
+
start the body with `<a data-asana-gid="<their user gid>"/>` (Asana expands it into a
|
|
29
|
+
proper mention). A comment without a mention may notify no one; reassignment alone is
|
|
30
|
+
easy to miss.
|
|
28
31
|
4. **Confirm before writing.** This posts to an external system. Show the user the chosen
|
|
29
32
|
assignee and the drafted comment and get a go-ahead, unless they've told you to proceed
|
|
30
33
|
without asking.
|
|
@@ -14,6 +14,13 @@ skill) so it stops living only in tribal memory.
|
|
|
14
14
|
`/auth` forms attach and enforces it **unconditionally** on `/oauth/{signup,signin}/request`
|
|
15
15
|
(fails closed). Deploy order matters: ship app-web **before** api, or the api blocks every
|
|
16
16
|
signin that arrives without a token. See `drawbridge-docs/user-stories/03-auth`.
|
|
17
|
+
- `BASIC_AUTH_USERNAME` + `BASIC_AUTH_PASSWORD` is the shared basic-auth staging-gate pair read
|
|
18
|
+
by **drawbridge-website** (`middleware.js`) and **drawbridge-app-web** (`proxy.js`) — same
|
|
19
|
+
names in both so one credential pair gates both dev deployments. The gate arms only when
|
|
20
|
+
**both** are set (fails open: a missing/misnamed var silently leaves the deployment public —
|
|
21
|
+
unset both in prod, set both in dev). Exempt: app-web `/api/health` (platform health checks)
|
|
22
|
+
and website Builder preview traffic. Not related to OAuth/session auth, which runs after the
|
|
23
|
+
gate unchanged.
|
|
17
24
|
|
|
18
25
|
## Sync owns reactive side effects
|
|
19
26
|
|
|
@@ -26,6 +33,13 @@ skill) so it stops living only in tribal memory.
|
|
|
26
33
|
`queue/index.js` together.
|
|
27
34
|
- BullMQ jobs are keyed on the change-stream resume token as `jobId` for HA dedup across sync
|
|
28
35
|
replicas. Reusing a static `jobId` with `removeOnComplete` makes re-enqueues no-op silently.
|
|
36
|
+
- Sync's `organization.connections` emit (stream/connection.js) doubles as app-web's cue to
|
|
37
|
+
refetch the server-built org menu (`['menu','organization',id]`), whose sidebar
|
|
38
|
+
Connections/Workflows warning dots reflect statuses `reconcileWorkflowStatus` writes — every
|
|
39
|
+
handler must emit **after** the reconcile (regression: sync test/connection-emit-order.test.js).
|
|
40
|
+
Emitting first hands the client a stale menu nothing re-emits to correct (the stuck-dot bug).
|
|
41
|
+
Workflow doc changes have **no** socket event, so app-web workflow status mutations
|
|
42
|
+
(pause/resume/delete) invalidate the menu client-side themselves.
|
|
29
43
|
- Scraped-asset file reuse keys on `organization + meta.origin + meta.element` **plus
|
|
30
44
|
`meta.render` for pipeline-rendered marks** (sync `resolveAsset` writes/queries it; the field
|
|
31
45
|
and its index live in drawbridge-api `schema/file.js`). `origin` identifies the source asset,
|
package/package.json
CHANGED