Skip to content

Commit 9193f40

Browse files
author
am
committed
fix(ci): complete the local agent fixture after merging main
merge current main without rewriting pr commits and supply the refresh callback required by the local agent source contract. Signed-off-by: am <6e30cd56c30e030cd31bb0939b94a7c257c9a09d5ba2d92cf2735da45629f248@buzz.block.builderlab.xyz>
2 parents 235907b + 99ec634 commit 9193f40

209 files changed

Lines changed: 15563 additions & 1042 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎docs/agents.md‎

Lines changed: 10 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -358,22 +358,16 @@ HTTP broker/verified transport, including corrupted signature rejection.
358358

359359
## Agent Activity plugin
360360

361-
**Agent Activity** is an independently toggleable bundled plugin that owns capture
362-
and the transcript panel. Conversation presentation uses a compact, floating
363-
avatar control above the composer, without a reserved strip or permanent avatar
364-
container. Hover, click, tap or keyboard opens **Working now**, reusing the sidebar's
365-
working-agent row. The row opens its known thread (or channel when no unique thread
366-
is known); a separate **View activity** action opens the agent's transcript.
367-
368-
The channel control includes work in threads. A thread control includes only
369-
exact-root evidence, never unconfirmed work. Current owner-visible turns provide
370-
brief tool status; unknown scopes fall back to channel activity. Multiple concurrent
371-
scopes never choose an arbitrary transcript thread. Public typing for the viewer's
372-
own `agentChoices` identities remains visible without telemetry; someone else's
373-
self-declared agent remains ordinary typing, without this owner-activity doorway.
374-
All projections consume existing stores and loaded profiles/channel rows, not new
375-
capture leases, relay reads or timers. A persistent, visually hidden status region
376-
announces working/typing transitions even when visual controls are absent.
361+
**Agent Activity** owns live capture demand and the full Transcript/Raw panel;
362+
host-owned saved history remains independent of plugin enablement. This branch
363+
adds an avatar-and-dots bubble beneath the exact message that triggered current
364+
work. Multiple turns group by agent; completing one turn does not hide another.
365+
Hover, click, tap or keyboard opens a compact avatar-and-latest-tool popup. Its
366+
row opens that exact agent's profile Activity tab, using the mainline transcript,
367+
conversation filtering and saved-history controls. Escape or outside click closes
368+
the popup. Human typing remains in the ordinary conversation indicator.
369+
370+
### Local plugin-agent lifecycle
377371

378372
The popup resets on conversation changes and when current work ends. Idle and
379373
historical activity remain accessible from the activity panel rather

‎docs/plugin-architecture.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -270,11 +270,11 @@ exact registration identity and mounted lifetime revoke callbacks on removal.
270270
The channel template extension point (`ctx.channelTemplates`) was removed with the
271271
v1 Agents system. The host sidebar owns personal groups and the existing + creation
272272
buttons. Channel templates are now device-local (`buzz.channel-templates.v1`,
273-
`features/channel-templates/local.ts`): a name, Agents team ids and a starting
274-
Canvas, managed under Settings → Channel templates. Picking one in Create resolves
275-
its teams to their members that are the owner's agents in this community and sends
276-
them with the Canvas as ordinary channel setup, which the session applies and
277-
retries as before.
273+
`features/channel-templates/local.ts`): a name, agent pubkeys, Agents team ids
274+
and a starting Canvas, managed under Settings → Channel templates. Picking one in
275+
Create resolves its agents and its teams' members to those that are the owner's
276+
agents in this community and sends them with the Canvas as ordinary channel setup,
277+
which the session applies and retries as before.
278278

279279
Hosted communities (`block.hosted-communities`) is a Block-specific bundled plugin
280280
under Settings → Communities. It manages Block-hosted relays through a Builderlab

‎docs/shell-design.md‎

Lines changed: 12 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -72,11 +72,20 @@ semantic tokens, UI authoring rules and the local component reference.
7272
tab. Each opening carries focus intent: topbar activation suppresses destination
7373
autofocus, while explicit New conversation, sidebar and deep-link openings keep
7474
their content focus. This intent is not saved in addresses or history; retry
75-
preserves it for the same opening. The selected page is a separately focusable,
75+
preserves it for the same opening. A focused Retry navigation control hands
76+
focus to main once retry removes it, even if reconnect temporarily remounts
77+
the shell. A new opening or focus elsewhere cancels this
78+
handoff. The selected page is a separately focusable,
7679
labelled tabpanel. Toolbar
7780
and overflow destinations remain native buttons using `aria-current` and
78-
focus main content on selection. Header pages never become companion launchers,
79-
and only the exact current page is selected.
81+
focus main content on selection. Header pages never become companion launchers.
82+
Independent header pages retain exact destination selection. Messages stays
83+
selected for registered sidebar/default-placement pages, including non-primary
84+
pages reached through search or links; their sidebar selection and route remain
85+
exact. Its tab labels the active child panel, and activating Messages from a
86+
child returns to the existing conversation view. More pages indicates this
87+
containing area with `aria-current="true"` (not `page`). Me and Settings remain
88+
separate; missing/unregistered destinations do not borrow Messages selection.
8089
The shell owns one joined Panel around navigation and page content, with a
8190
16px outer gutter (8px on narrow screens). Nested Panels keep their opaque
8291
fill and clipping but drop individual borders, radii, and shadows. Layout

‎docs/workflows.md‎

Lines changed: 28 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -173,18 +173,42 @@ records carry reusable verification evidence; unsigned local intent, copied
173173
caller proof symbols and ordinary senders cannot establish it. No signature
174174
verification runs while folding retained history.
175175

176+
The owner tag identifies the identity that scheduled the workflow, not the author
177+
of every rendered word. Templates can include trigger-controlled values; those
178+
values do not acquire the owner's prompt authority.
179+
180+
Claude Code and Codex also use this proof to authorize delegated workflow mentions.
181+
The receiving agent's ready community session must supply the explicit relay
182+
authority. The workflow owner must be that agent's owner, or an agent whose
183+
admitted kind-0 profile cryptographically proves the same owner through NIP-OA.
184+
The profile comes from the receiving agent's community profile directory;
185+
display metadata and saved inventories do not prove sibling ownership. Missing,
186+
invalid or failed profile reads deny the mention; a later mention can retry.
187+
Both runtimes recheck delivery cancellation after authorization, before creating
188+
sessions or starting processes, so removing an agent during a profile read cannot
189+
restart it when the read completes.
190+
The event must contain a canonical `buzz:workflow-mention` for the receiving
191+
agent; all such tags
192+
must have exactly two fields, a lowercase-hex pubkey, and no duplicate targets.
193+
The relay emits these tags only for targets present in the owner-authored template
194+
and the rendered output. Legacy `p` tags route mentions but do not authorize them.
195+
Workflows created and maintained under an owned agent's own key remain owned by
196+
that agent and can wake agents with the same proven human owner. This does not
197+
grant an agent permission to edit a workflow owned by a different signing identity.
198+
176199
Cached-only startup intentionally shows the actual signer until a live connection
177200
establishes explicit relay authority. Saved operator-contact `relayAuthor` is not
178201
promoted to `self`, and no new trusted storage is introduced. Signer-based search
179-
and Inbox sender filters, permissions, mention policy and relay-reported participant
202+
and Inbox sender filters and relay-reported participant
180203
summaries are unchanged by workflow presentation. Channel/thread rows retain the
181204
effective-author attribution and owner edit/delete behavior added separately in
182205
#661; when that author differs from the signer, the row carries a separate signing
183206
key so the disclosure still identifies the actual relay. Thread and media views
184207
request workflow-owner profiles through the existing background profile directory.
185-
The workflow proof check controls only the automation label, not main's effective
186-
message-author policy. With explicit authority, an unadmitted copy has no workflow
187-
label but can still receive main's effective-author attribution; production reads
208+
The workflow proof controls the automation label and the delegated-mention gate
209+
above; it does not control main's effective message-author policy. With explicit
210+
authority, an unadmitted copy has neither a workflow label nor delegated prompt
211+
authority, but can still receive main's effective-author attribution; production reads
188212
must retain their admission-owned event objects. Without explicit authority,
189213
cached-only startup keeps the signer fallback described above.
190214
Participant summaries have no per-message owner evidence

‎patches/@[email protected]‎

Lines changed: 152 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -258,3 +258,155 @@ index ef202bd782287091b2a7d0d179fe5d43c4ff73a3..34d5f2b811eb9412c071f3340c575d14
258258
const defaultProps = {
259259
id: idProp,
260260
role: 'radiogroup',
261+
diff --git a/floating-ui-react/hooks/useHoverReferenceInteraction.d.mts b/floating-ui-react/hooks/useHoverReferenceInteraction.d.mts
262+
index 9f3ac4b14b6bd2caeef52ce284e1d22d1ba007fe..f12bffd0ef926ade984240b9a1e2c4b1cc13babc 100644
263+
--- a/floating-ui-react/hooks/useHoverReferenceInteraction.d.mts
264+
+++ b/floating-ui-react/hooks/useHoverReferenceInteraction.d.mts
265+
@@ -25,7 +25,7 @@ export interface UseHoverReferenceInteractionProps {
266+
* Called before each hover-driven open attempt (immediate, delayed, and rest-ms
267+
* paths). Return `false` to veto; any other return value permits the open.
268+
*/
269+
- shouldOpen?: (() => boolean) | undefined;
270+
+ shouldOpen?: ((event: MouseEvent) => boolean) | undefined;
271+
/**
272+
* Regression workaround (#5152): also cancels a pending hover-open from the
273+
* trigger's `mouseout`, backing up a `mouseleave` that Chrome can drop during
274+
diff --git a/floating-ui-react/hooks/useHoverReferenceInteraction.d.ts b/floating-ui-react/hooks/useHoverReferenceInteraction.d.ts
275+
index 7551ed4a6cc55fe7c2c9973670c8dcaff650ba2f..c9a80f623b357233e5eeeadcf0762697175f84d9 100644
276+
--- a/floating-ui-react/hooks/useHoverReferenceInteraction.d.ts
277+
+++ b/floating-ui-react/hooks/useHoverReferenceInteraction.d.ts
278+
@@ -25,7 +25,7 @@ export interface UseHoverReferenceInteractionProps {
279+
* Called before each hover-driven open attempt (immediate, delayed, and rest-ms
280+
* paths). Return `false` to veto; any other return value permits the open.
281+
*/
282+
- shouldOpen?: (() => boolean) | undefined;
283+
+ shouldOpen?: ((event: MouseEvent) => boolean) | undefined;
284+
/**
285+
* Regression workaround (#5152): also cancels a pending hover-open from the
286+
* trigger's `mouseout`, backing up a `mouseleave` that Chrome can drop during
287+
diff --git a/floating-ui-react/hooks/useHoverReferenceInteraction.js b/floating-ui-react/hooks/useHoverReferenceInteraction.js
288+
index 9c5f5bae91441c732a0def38caf2ca655c7d7aae..1be80667032ff899e5cb11db652bf9063077900f 100644
289+
--- a/floating-ui-react/hooks/useHoverReferenceInteraction.js
290+
+++ b/floating-ui-react/hooks/useHoverReferenceInteraction.js
291+
@@ -62,8 +62,8 @@ function useHoverReferenceInteraction(context, props = {}) {
292+
const isClickLikeOpenEvent = (0, _useStableCallback.useStableCallback)(() => {
293+
return (0, _useHoverShared.isClickLikeOpenEvent)(dataRef.current.openEvent?.type, instance.interactedInside);
294+
});
295+
- const checkShouldOpen = (0, _useStableCallback.useStableCallback)(() => {
296+
- return shouldOpenRef.current?.() !== false;
297+
+ const checkShouldOpen = (0, _useStableCallback.useStableCallback)(event => {
298+
+ return shouldOpenRef.current?.(event) !== false;
299+
});
300+
const isOverInactiveTrigger = (0, _useStableCallback.useStableCallback)((currentDomReference, currentTarget, target) => {
301+
const allTriggers = store.context.triggerElements;
302+
@@ -184,7 +184,7 @@ function useHoverReferenceInteraction(context, props = {}) {
303+
// Open immediately when moving between triggers while open, or during
304+
// a hover-driven close transition (including same-trigger re-entry).
305+
if (shouldOpenImmediately) {
306+
- if (checkShouldOpen()) {
307+
+ if (checkShouldOpen(event)) {
308+
store.setOpen(true, (0, _createBaseUIEventDetails.createChangeEventDetails)(_reasons.REASONS.triggerHover, event, triggerNode));
309+
}
310+
return;
311+
@@ -194,12 +194,12 @@ function useHoverReferenceInteraction(context, props = {}) {
312+
}
313+
if (openDelay) {
314+
instance.openChangeTimeout.start(openDelay, () => {
315+
- if (shouldOpen && checkShouldOpen()) {
316+
+ if (shouldOpen && checkShouldOpen(event)) {
317+
store.setOpen(true, (0, _createBaseUIEventDetails.createChangeEventDetails)(_reasons.REASONS.triggerHover, event, triggerNode));
318+
}
319+
});
320+
} else if (shouldOpen) {
321+
- if (checkShouldOpen()) {
322+
+ if (checkShouldOpen(event)) {
323+
store.setOpen(true, (0, _createBaseUIEventDetails.createChangeEventDetails)(_reasons.REASONS.triggerHover, event, triggerNode));
324+
}
325+
}
326+
@@ -312,7 +312,7 @@ function useHoverReferenceInteraction(context, props = {}) {
327+
return;
328+
}
329+
const latestOpen = store.select('open');
330+
- if (!instance.blockMouseMove && (!latestOpen || isOverInactive) && checkShouldOpen()) {
331+
+ if (!instance.blockMouseMove && (!latestOpen || isOverInactive) && checkShouldOpen(nativeEvent)) {
332+
store.setOpen(true, (0, _createBaseUIEventDetails.createChangeEventDetails)(_reasons.REASONS.triggerHover, nativeEvent, trigger));
333+
}
334+
}
335+
diff --git a/floating-ui-react/hooks/useHoverReferenceInteraction.mjs b/floating-ui-react/hooks/useHoverReferenceInteraction.mjs
336+
index 01ec377e5046cf1645dbd2203e8c6dc99a89ea18..659a8dc07135f8a82e03b654d514c4f2a010cb4c 100644
337+
--- a/floating-ui-react/hooks/useHoverReferenceInteraction.mjs
338+
+++ b/floating-ui-react/hooks/useHoverReferenceInteraction.mjs
339+
@@ -56,8 +56,8 @@ export function useHoverReferenceInteraction(context, props = {}) {
340+
const isClickLikeOpenEvent = useStableCallback(() => {
341+
return isClickLikeOpenEventShared(dataRef.current.openEvent?.type, instance.interactedInside);
342+
});
343+
- const checkShouldOpen = useStableCallback(() => {
344+
- return shouldOpenRef.current?.() !== false;
345+
+ const checkShouldOpen = useStableCallback(event => {
346+
+ return shouldOpenRef.current?.(event) !== false;
347+
});
348+
const isOverInactiveTrigger = useStableCallback((currentDomReference, currentTarget, target) => {
349+
const allTriggers = store.context.triggerElements;
350+
@@ -178,7 +178,7 @@ export function useHoverReferenceInteraction(context, props = {}) {
351+
// Open immediately when moving between triggers while open, or during
352+
// a hover-driven close transition (including same-trigger re-entry).
353+
if (shouldOpenImmediately) {
354+
- if (checkShouldOpen()) {
355+
+ if (checkShouldOpen(event)) {
356+
store.setOpen(true, createChangeEventDetails(REASONS.triggerHover, event, triggerNode));
357+
}
358+
return;
359+
@@ -188,12 +188,12 @@ export function useHoverReferenceInteraction(context, props = {}) {
360+
}
361+
if (openDelay) {
362+
instance.openChangeTimeout.start(openDelay, () => {
363+
- if (shouldOpen && checkShouldOpen()) {
364+
+ if (shouldOpen && checkShouldOpen(event)) {
365+
store.setOpen(true, createChangeEventDetails(REASONS.triggerHover, event, triggerNode));
366+
}
367+
});
368+
} else if (shouldOpen) {
369+
- if (checkShouldOpen()) {
370+
+ if (checkShouldOpen(event)) {
371+
store.setOpen(true, createChangeEventDetails(REASONS.triggerHover, event, triggerNode));
372+
}
373+
}
374+
@@ -306,7 +306,7 @@ export function useHoverReferenceInteraction(context, props = {}) {
375+
return;
376+
}
377+
const latestOpen = store.select('open');
378+
- if (!instance.blockMouseMove && (!latestOpen || isOverInactive) && checkShouldOpen()) {
379+
+ if (!instance.blockMouseMove && (!latestOpen || isOverInactive) && checkShouldOpen(nativeEvent)) {
380+
store.setOpen(true, createChangeEventDetails(REASONS.triggerHover, nativeEvent, trigger));
381+
}
382+
}
383+
diff --git a/menu/submenu-trigger/MenuSubmenuTrigger.js b/menu/submenu-trigger/MenuSubmenuTrigger.js
384+
index 76610266064c56e99741296140b0db02d8b7ab04..66f90d4389411580f5aef91a8198686ee814011b 100644
385+
--- a/menu/submenu-trigger/MenuSubmenuTrigger.js
386+
+++ b/menu/submenu-trigger/MenuSubmenuTrigger.js
387+
@@ -146,7 +146,9 @@ const MenuSubmenuTrigger = exports.MenuSubmenuTrigger = /*#__PURE__*/React.forwa
388+
open: delay,
389+
close: closeDelay
390+
},
391+
- shouldOpen: delay > 0 ? () => parentMenuStore.select('allowMouseEnter') : undefined,
392+
+ // A newly opened parent can appear beneath a stationary pointer.
393+
+ // Zero delay still requires pointer movement before activating its submenu.
394+
+ shouldOpen: event => parentMenuStore.select('allowMouseEnter') || delay === 0 && event.type === 'mousemove',
395+
triggerElementRef,
396+
externalTree: floatingTreeRoot,
397+
isClosing: () => store.select('transitionStatus') === 'ending',
398+
diff --git a/menu/submenu-trigger/MenuSubmenuTrigger.mjs b/menu/submenu-trigger/MenuSubmenuTrigger.mjs
399+
index 243ee5ac67bbb0297a3ede21f3963372c43c0150..341beb1f7a2093e68d1bd65fae62c7712a657d11 100644
400+
--- a/menu/submenu-trigger/MenuSubmenuTrigger.mjs
401+
+++ b/menu/submenu-trigger/MenuSubmenuTrigger.mjs
402+
@@ -139,7 +139,9 @@ export const MenuSubmenuTrigger = /*#__PURE__*/React.forwardRef(function MenuSub
403+
open: delay,
404+
close: closeDelay
405+
},
406+
- shouldOpen: delay > 0 ? () => parentMenuStore.select('allowMouseEnter') : undefined,
407+
+ // A newly opened parent can appear beneath a stationary pointer.
408+
+ // Zero delay still requires pointer movement before activating its submenu.
409+
+ shouldOpen: event => parentMenuStore.select('allowMouseEnter') || delay === 0 && event.type === 'mousemove',
410+
triggerElementRef,
411+
externalTree: floatingTreeRoot,
412+
isClosing: () => store.select('transitionStatus') === 'ending',

‎pnpm-lock.yaml‎

Lines changed: 3 additions & 3 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)