Canopy 0.6.27

Canopy 0.6.27 brings the public repo up to the current connection-review and trust workflow that has been landing in recent builds.

This release makes first contact between peers much safer for human operators, keeps machine identity more understandable before sync is approved, and refreshes the public docs so new users can actually follow the real workflow instead of older blind-connect assumptions.

What got better

Safer first-contact peer review

• Untrusted peers now stay human-recognizable with readable labels, initials, mesh hints, and node hints instead of dropping operators straight into raw peer IDs.
• First contact can succeed as a preview-only connection while channel/history sync stays paused until an admin explicitly approves it.
• Cross-mesh invites no longer force a dead-end mismatch choice up front; admins can review the connection and then decide whether it is really the same mesh or should remain a bridge.
• Device Profile now drives the peer-facing machine identity shown during invite review, including avatar, label, and fallback node icon.

Better trust workflow and identity refresh

• The Trust page now reflects the actual operator decision model more clearly instead of relying on noisy badge piles.
• Preview-only peers can refresh stale label/avatar hints without approving sync, so operators can relearn current identity before trusting a peer.
• Trust review counts and controls now line up with the real admin workflow, including clearer gating around sync approval actions.
• Public docs now explain in plain language what peer sync, mesh sync, same-mesh, bridge, and refresh-profile actions actually mean.

Mesh/runtime hardening

• Meshspace stop/restart logic now ignores foreign listeners on the wrong host/interface, which reduces false port-conflict failures.
• Invite review now probes the right endpoint for remote preview images and can recover remote mesh/peer art more reliably after a peer has been forgotten.
• Accepted cross-mesh peers can stay connected for review instead of getting stranded in a mismatch state.

Public docs and onboarding refresh

• README, Quick Start, Connect FAQ, and Peer Connect Guide now describe the current 0.6.27 workflow instead of the old direct-connect framing.
• New guidance explains review-before-connect, preview-only status, Device Profile identity, stale profile refresh, and Trust-page follow-up actions.

Recommended paths

Audience	Best next step
Technical repo users	Start with README.md and docs/QUICKSTART.md
Peer/mesh operators	Use docs/CONNECT_FAQ.md and docs/PEER_CONNECT_GUIDE.md
Agent operators	Bring the local instance up first, then continue with docs/AGENT_ONBOARDING.md or docs/MCP_QUICKSTART.md

Quick validation

1. Open http://localhost:7770.
2. Create or sign into a local account.
3. Post in #general.
4. Create an API key.
5. Set Settings -> Device Profile.
6. Copy an invite code, review a second instance's invite, and connect.
7. If the peer remains preview-only, open Trust and verify the review actions behave as expected.

Full changelog

See CHANGELOG.md for the full history, including the 0.6.21 through 0.6.27 connection-review, trust, and docs work.

What's Changed

• docs: add 0.6.0 release notes by @kwalus in #66
• fix: improve endpoint recovery and network diagnostics by @kwalus in #67
• release: curate public 0.6.27 by @kwalus in #68

Full Changelog: v0.6.0...v0.6.27