2026-05-22Release link
Referral + squad invitation architecture (POC-160) + full invite lifecycle polish
Completed the growth/virality architecture: users can now invite partners, contractors, agents, and lenders into private squads via published profile search + pending invites (building on POC-171). Shared workflows (pipeline, leads, comments) fully enabled via existing team RLS. Added sent/pending revoke flows, richer invite details (names via joins), and documented referral incentives plan. Referral acquisition and squad collaboration now form the documented end-to-end loop.
- Enhanced lib/teams.ts (was network.ts) with enrichTeamInvitations + richer listPending* (team/inviter/invitee names populated for UI).
- app/network/page.tsx: richer received invites, per-team sent pending list + revoke buttons (new revokeTeamInviteAction).
- app/workspace/actions.ts: revokeTeamInviteAction wired.
- docs/referral-system.md: new sections on squad integration + planned incentives (track-only today; future metrics-based post-launch).
- lib/changelog.ts + INTERNAL_CHANGELOG.md updated with POC-160 evidence (file:line).
- All ACs met: invite 4 roles (owner/partner/analyst/operator mapping to partners/contractors/agents/lenders), shared workflows (RLS 0007+). Incentives planned at time (later POC-502). Pre-work deep map + PLAN.md produced.
- Post-merge: PR #228 + #230 (see 2026-06 main) advanced 'shared workflows enabled' AC with team-scoped leadFunnel + handoff actions now usable by squad members (lib/lead-flow.ts, lib/marketplace/workspace-status.ts + tests).
