Files
buzz/desktop/src/features/projects/projectOwnerControl.ts
thomaspblock 122a8b8988 Projects v3: unify sharing, discussions, and issue ownership (#5792)
## Summary

Projects v3 makes repository work shareable, discussion-aware, and
easier to scan in one coherent workspace. People can copy canonical
links, reopen the exact workspace tab, understand issue and pull-request
context at a glance, find related channel conversations, and assign or
unassign issues across Desktop and CLI.

- **Unified workspace** — top-level sections sit above repository
controls in one rounded workspace, with navigation positioned close to
the page heading. README and Files retain branch selection; every
section has a labeled icon header, and Issues and Pull Requests expose
creation from a consistent right-aligned action.
- **Repository management** — the repository selector is always
available, including single-repository projects. Its integrated add flow
lets project owners create a repository manually or select an existing
repository without a separate toolbar button.
- **Readable work-item lists** — issue and pull-request rows use
plain-language context instead of opaque metadata. Files, commits,
issues, pull requests, channels, and contributors share consistent row
density and right-aligned timestamps, while deterministic
fallback-avatar colors keep participants distinct on light backgrounds.
Inbox pull-request metadata wraps between complete phrases and truncates
long channel names instead of compressing copy into narrow columns.
- **Reliable entity links** — projects, repositories, issues, pull
requests, and commits have canonical `buzz://` links, preview cards, OS
deep-link routing, and tab-aware navigation. Reopening the same link
re-applies its destination instead of leaving the user on a locally
selected tab.
- **Related conversations** — repository and work-item views surface
channels discussing the current entity, including participants, channel
navigation, message context, and an explicit notice when discovery
reaches its 500-result cap.
- **Reversible issue ownership** — trusted assignment and unassignment
events work across Desktop, Tauri, `buzz-sdk`, and `buzz issues`.
Assignees appear in project views and the assigned inbox, while
authorized users can remove assignments directly from the assignee row.

Assignment state is derived chronologically from labeled Nostr notes.
Issue authors and repository owners may change any assignee; other users
may only assign or unassign themselves. Shared golden fixtures keep
entity-link grammar and validation aligned across TypeScript and Rust.

The branch also updates `webbrowser` to the patched release for
RUSTSEC-2026-0257.

### Related issue

N/A.

### Testing

- [x] `just ci` — formatting, lint, typechecking, unit tests, and builds
passed
- [x] Full pre-push suite — organization, branch-skew, Desktop checks,
typechecking, and tests passed on the latest push
- [x] `cargo test -p buzz-cli` and focused `buzz-sdk` assignment tests
passed
- [x] Focused Tauri recipient-note and 500-result search-limit tests
passed
- [x] Desktop entity-link and issue-assignment unit tests passed
- [x] Playwright smoke coverage passed for assignment, repeated
entity-link navigation, repository create/select flows, section headers
and actions, timestamp alignment, timeline icons, sentence-style
issue/PR metadata, header spacing, avatar contrast, and Inbox metadata
at stacked and side-rail breakpoints
- [ ] Manual staging pass: link round-trips, Channels tab, assignment
flows, and inbox routing

### Screenshots

Pull requests explain who opened the request, where it lives, and which
branch it comes from; fallback avatars remain visually distinct.

![Pull request list with conversational
metadata](https://raw.githubusercontent.com/block/buzz/2a536de86f7e6f79b349d7bc147b2923ff2b817d/pr-5624--05-pr-list-metadata.png)

Issues use the same sentence-style hierarchy while keeping status and
recency easy to scan.

![Issue list with conversational
metadata](https://raw.githubusercontent.com/block/buzz/2a536de86f7e6f79b349d7bc147b2923ff2b817d/pr-5624--06-issue-list-metadata.png)

The wide Inbox detail keeps author, timestamp, and origin context
readable beside its metadata rail.

![Pull request Inbox detail with readable
metadata](https://raw.githubusercontent.com/block/buzz/e65b433e14b97c45365ed7b68ea402ec01d26615/pr-5624--02-pull-request-detail-wide.png)

[View the complete six-state Projects v3 screenshot
set](https://github.com/block/buzz/pull/5624#issuecomment-5268039672)
and [the compact/wide Inbox
comparison](https://github.com/block/buzz/pull/5624#issuecomment-5268614585).


---

> Supersedes #5624, whose head commit accumulated permanently-queued
required check suites (block-dco-check et al.) that GitHub never
dispatched. History flattened into a single signed-off commit on latest
main; tree verified byte-identical (`git merge-tree`) to merging the
original branch into main.

---------

Signed-off-by: Thomas Petersen <thomasp@squareup.com>
Co-authored-by: Wintermute <3f1797424fd9ad6653a83665c660517777cd7f8c228c0d5907f49e01537f3ca5@buzz.block.builderlab.xyz>
2026-08-14 16:48:41 -04:00

129 lines
4.2 KiB
TypeScript

import { subscribeControlResults } from "@/features/agents/observerRelayStore";
import { sendAgentObserverControl } from "@/shared/api/observerRelay";
import type { RelayEvent } from "@/shared/api/types";
import {
KIND_PROJECT_ANNOUNCEMENT,
KIND_REPO_ANNOUNCEMENT,
} from "@/shared/constants/kinds";
const OWNER_CONTROL_TIMEOUT_MS = 20_000;
export type ProjectOwnerAnnouncementTemplate = {
kind: number;
content: string;
createdAt?: number;
tags: string[][];
};
type ProjectOwnerControlResult = {
type: "publish_project_owner_announcements";
status: string;
requestId: string;
events?: RelayEvent[];
error?: string | null;
};
/**
* A remote-agent publish that failed after some announcements already landed.
* `publishedEvents` holds the events the ACP side reported as live before the
* failure, so callers can tell a clean failure (retry republishes everything)
* from a partial one (retry must resume from where publication stopped).
*/
export class PartialAnnouncementPublishError extends Error {
readonly publishedEvents: RelayEvent[];
constructor(message: string, publishedEvents: RelayEvent[]) {
super(message);
this.name = "PartialAnnouncementPublishError";
this.publishedEvents = publishedEvents;
}
}
/**
* True when a failed [project, repository] announcement publish stopped
* exactly between its two events — the project head landed, the repository
* event did not. That is the only partial state addRepo can resume from by
* republishing just the repository event; anything else must surface.
*/
export function isDanglingProjectMemberPublish(
error: unknown,
): error is PartialAnnouncementPublishError {
return (
error instanceof PartialAnnouncementPublishError &&
error.publishedEvents.some(
(event) => event.kind === KIND_PROJECT_ANNOUNCEMENT,
) &&
!error.publishedEvents.some(
(event) => event.kind === KIND_REPO_ANNOUNCEMENT,
)
);
}
/** Ask a remotely managed agent to publish project events under its own key. */
export function publishOwnedAgentProjectAnnouncements(
agentPubkey: string,
announcements: ProjectOwnerAnnouncementTemplate[],
): Promise<RelayEvent[]> {
const requestId = crypto.randomUUID();
return new Promise((resolve, reject) => {
let settled = false;
const finish = (
result: { events: RelayEvent[] } | { error: Error },
): void => {
if (settled) return;
settled = true;
window.clearTimeout(timeout);
unsubscribe();
if ("error" in result) reject(result.error);
else resolve(result.events);
};
const unsubscribe = subscribeControlResults(agentPubkey, (frame) => {
const projectFrame = frame as unknown as ProjectOwnerControlResult;
if (
projectFrame.type !== "publish_project_owner_announcements" ||
projectFrame.requestId !== requestId
) {
return;
}
if (projectFrame.status === "ok" && projectFrame.events) {
finish({ events: projectFrame.events });
} else {
const message =
projectFrame.error || "The agent could not update this project.";
// The ACP side publishes announcements sequentially and reports the
// ones that were already live when a later one failed. Preserve that
// partial-success metadata instead of discarding it, so callers can
// resume publication rather than treating the state as unrecoverable.
const published = projectFrame.events ?? [];
finish({
error:
published.length > 0
? new PartialAnnouncementPublishError(message, published)
: new Error(message),
});
}
});
const timeout = window.setTimeout(() => {
finish({
error: new Error(
"The project owner agent did not respond. Make sure it is running and try again.",
),
});
}, OWNER_CONTROL_TIMEOUT_MS);
void sendAgentObserverControl(agentPubkey, {
type: "publish_project_owner_announcements",
requestId,
announcements,
}).catch((error: unknown) => {
finish({
error:
error instanceof Error
? error
: new Error("Failed to contact the project owner agent."),
});
});
});
}