Skip to content

feat(relay): complete packaged community access and recovery - #338

Merged
wesbillman merged 5 commits into
mainfrom
deep-links-part-2
Sep 28, 2026
Merged

wesbillman merged 5 commits into
mainfrom
deep-links-part-2

Conversation

@matt2e

@matt2e matt2e commented Sep 28, 2026

Copy link
Copy Markdown
Contributor

Summary:

  • Add native relay bridge support for packaged community access and recovery.
  • Preserve community admission recovery intent across the join flow.
  • Document the packaged relay/recovery behavior and add native relay, community join, browser, and demo coverage.

Testing:

  • Not run during PR creation; branch validation was completed before this step.

Connect the persisted native identity to community admission, authenticated HTTP and live relay traffic. Keep credentials in the native owner and preserve scoped session and outbox ownership.

Journal unfinished joins, require local membership persistence, recover uncertain claims and profiles after restart, and read back expired delivery without re-dating events. Cover native IPC signing and browser reload recovery; document remaining packaged acceptance limits.

Signed-off-by: Matt Toohey <contact@matttoohey.com>
Verify the current profile after acknowledged publication before saving membership or clearing recovery. Retain drafts through read failures, missing or superseded profiles, and stale completions.

Persist canonical journal origins, retain unresolved legacy aliases independently, and preserve the newest draft when restored mappings overlap. Add regression coverage for both P2 findings and recovery boundaries, and update the manual fixture and ownership documentation.

Signed-off-by: Matt Toohey <contact@matttoohey.com>
Add an isolated full-app IPC fixture and paced recordings for all requested identity, admission, messaging, persistence, profile, and alias recovery flows from 78d986c and d6f0748.

Generate labeled H.264 videos, timestamp mappings, assertion evidence, and playback verification locally. Document mocked boundaries and deferred native acceptance; keep artifacts out of Git.

Signed-off-by: Matt Toohey <contact@matttoohey.com>
@matt2e
matt2e requested review from a team, comp615 and wesbillman as code owners September 28, 2026 06:36

@wesbillman wesbillman left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Star Lord automated source review

Submitted through Wes's account; non-blocking COMMENT only.

No actionable source-demonstrated findings at this revision.

  • Head: f68926dadf5a5f9a5aa1a610eee5d5e07b11200c
  • Target base: 85d6bf82c54d1c8d930d58444597a1fe31cc8975
  • PR merge base: 59d9d6fb9e22771ad9d380900d4c9d7fe152219c

Reviewed the 42-file PR diff and relevant callers: native identity signing/IPC permissions, HTTPS route and redirect handling, native adapter composition and live ownership, shared HTTP admission and durable-outbox retry semantics, community admission/profile verification and journal persistence, session restoration, and regression/demo sources. Cross-checked the overlapping target-branch changes to native command registration. Downloaded source blobs were hash-verified; no dirty checkout inputs were used.

Validation limits: source inspection only. I ran no PR code, tests, builds, demo scripts, or app processes, and did not evaluate CI in this cycle. Checked-in browser/demo results are contributor-reported fixture evidence, not independent native acceptance. Keychain consent/denial and identity persistence, installed-app live read/send/receipt/restart, production TLS/relay interoperability, and release signing remain unverified. NIP-FI acquisition and the documented absent native capabilities are outside this slice. This is not approval or merge authorization.

Remove the capture, simulated host, scenarios, media finishing scripts, and documentation added for native admission and recovery recordings.

Preserve production relay and recovery code, regression tests, and the ignore rule for existing local recordings.

Signed-off-by: Matt Toohey <contact@matttoohey.com>
Rename the browser recovery fixture, IPC bridge, and screenshot to identify mocked native IPC. Label the fixture page and document its origin, real browser boundaries, and distinction from the removed recording toolkit.

Signed-off-by: Matt Toohey <contact@matttoohey.com>

@wesbillman wesbillman left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Star Lord automated source follow-up

Submitted through Wes's account; non-blocking COMMENT only.

No actionable source-demonstrated findings in this follow-up.

  • Head: 610e07d91097b15d25aea4b7b68480b44e06e31e
  • Target base: 85d6bf82c54d1c8d930d58444597a1fe31cc8975
  • Incremental scope: changes since the previously reviewed f68926dadf5a5f9a5aa1a610eee5d5e07b11200c (review #5334936506): removal of the manual recording toolkit, rename/labeling of the mocked native-IPC browser fixture, and provenance documentation. Production implementation is unchanged in this delta.

Checked the renamed spec → HTML → TSX → exposed IPC wiring, preserved reload/storage/retry assertions, and browser discovery through the local and CI configurations for both engines. A search of the pinned repository's UTF-8 regular files found no remaining references to the old fixture names or removed toolkit paths; the intentional ignored recordings directory remains. The documentation now distinguishes browser-fixture evidence from native/live-relay acceptance. Source files were Git-blob-hash verified; no dirty checkout inputs were used.

Validation limits: source inspection only; no PR code, tests, builds, demos, or app processes executed. CI was not assessed in this cycle. Browser assertions and documented regression results were not independently rerun. Native-process restart, Keychain behavior, production TLS/deployed-relay interoperability, and signed/notarized release acceptance remain unverified. This is not approval or merge authorization.

@wesbillman
wesbillman merged commit f551b81 into main Sep 28, 2026
14 checks passed
@wesbillman
wesbillman deleted the deep-links-part-2 branch September 28, 2026 17:40
johnmatthewtennant pushed a commit that referenced this pull request Sep 29, 2026
* origin/main:
  Keep custom emoji animated in reactions (#354)
  Polish community dialogs, agent cards, and conversation controls (#342)
  fix(channels): paginate membership discovery beyond 500 channels (#326)
  Remove local project context from docs (#350)
  feat(github): render PR descriptions with inline media (#335)
  feat(dev): measure channel opens, warming cost and live setup (#315)
  fix(agents): start new agents on Create and make their status clear (#332)
  fix(macos): close the window without quitting Buzz (#349)
  fix: allow parallel desktop dev worktrees (#336)
  feat(relay): complete packaged community access and recovery (#338)
  fix(workflows): clarify controls and align compact workflow UI (#337)
  feat: add custom emoji from settings (#346)
  feat(channels): show typing status on sidebar dm rows (#305)
  fix(workflows): page batched definition reads (#325)

Signed-off-by: Sol <49aa1f65411fd096d2e2ec144f1e7aa36fdc76d1b907cfdf7be000c66f9d3b8e@buzz.block.builderlab.xyz>

# Conflicts:
#	src/bundled/agents/AgentsPage.tsx
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants