feat(team-sync): #279 Phase 2 — team-mode integration for sync-and-brief

[Knapp-Kevin]

Summary

Phase 2 of #279. Wires the existing `BackendAdapter` interface (shipped in #277) into the `sync-and-brief` CLI flow. The team-mode complement to Phase 1's solo-mode session magic (PR #318, merged).

Order invariants

1. BEFORE source pull: `backend.pull_events()` copies every peer's `.jsonl` into the local `.bicameral/events/` cache. The materializer's existing `*.jsonl` glob picks them up alongside the operator's own events. Peer ingest is visible in the brief without manual action.
2. AFTER source ingest succeeds: `backend.push_events()` uploads each local `.jsonl` to the shared backend. LocalFolderAdapter's sha-match skip keeps re-invocations idempotent.

Failure modes (non-blocking by design)

Scenario	Behavior
`team:` absent from config	Solo mode. No backend constructed.
`team.backend` set, `team.author` empty	Warning to stderr; team sync skipped; CLI continues local-only.
Backend `pull_events` raises	Logged; continues with current local events_dir state.
Backend `push_events` raises for one file	Logged; other files still pushed.
Source ingest raises	Watermark NOT advanced (Phase 1 invariant); push still runs for unrelated files.

Brief renderer extension

The brief gains an optional `## Team sync` section showing `peer_files_pulled` + `my_file_pushed`. Omitted entirely when `team_sync=None` so solo-mode briefs render byte-identically to pre-Phase-2.

Per-#205 doctrine alignment

The only operator-facing default in this new code path — "no team backend when `team:` config is absent" — is a deterministic gate at `events/backends/init.py::get_backend` (returns `None`), NOT a skill-text-only claim. Backend errors return `None` safely. Per the doctrine just shipped in PR #320.

Test plan

• `python -m pytest tests/test_sync_and_brief_team_mode.py -v` — 12 tests sociable per CLAUDE.md (real `LocalFolderAdapter`, real `BicameralContext`, real file system; no backend mocks)
• `python -m pytest tests/test_brief_renderer.py -v` — 3 new tests for the `## Team sync` section
• Full Phase 1 + Phase 2 + brief + sessionstart sweep — 56 passed
• Manual: configure two real repos with shared `remote_root` + matching `team:` blocks; run sync-and-brief on machine A, then machine B; verify A's events appear in B's brief

Headline test: two-machine round-trip

`test_team_sync_round_trip_alice_to_bob_via_local_folder` — spans Alice's repo → shared `remote_root` → Bob's repo and verifies Alice's events land in Bob's cache after his next `sync-and-brief`. End-to-end across two `BicameralContext` instances + a real shared `LocalFolderAdapter`. No mocks on the backend, materializer, or file system.

Files

Path	Change
`cli/sync_and_brief_cli.py`	Add `_resolve_team_backend`, `_team_sync_pull`, `_team_sync_push`; wire into `_run` around the source-pull loop
`cli/brief_renderer.py`	Optional `team_sync` kwarg; `## Team sync` section
`tests/test_sync_and_brief_team_mode.py`	12 new integration tests including the two-machine round-trip
`tests/test_brief_renderer.py`	3 new tests for the team-sync section
`docs/policies/sources-config.md`	New "Team backend" section documenting config schema + failure modes

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 5aa9ffad-9f87-4e41-85b9-5f9dbc548ef8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/279-phase2-team-mode-integration

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}