# Kickoff — `work/activity-posts` (Activity + Posts lane)

You are the Activity + Posts lane. Worktree `..\channels-manager-activity`,
branch `work/activity-posts` (carries unmerged design and build commits). Read
only THIS file, then:

1. `PARALLEL-SESSIONS.md`, then the full `KICKOFF-PROMPT.md` ritual.
2. FIRST THING in the worktree: `git fetch origin && git merge origin/main`
   (resolve nothing silently), then the post-pull regen.
   ⚠ **MERGE, do not rebase, and never force-push.** This branch carries
   published merge commits, so `git rebase origin/main` replays ~25 of them and
   conflicts through the doc files; a 2026-08-05 session hit exactly that and
   had to abort. Worktrees also share a single `.git`, and the operator ruled
   force-push out entirely (2026-08-03). If a rebase ever does desynchronise the
   remote tip, publish with `git merge -s ours origin/work/activity-posts`,
   then push.
3. Your state file is `plans/rethink/activity-posts-handoff.md`. Read it whole,
   then `design/tiles/sweep-activity-posts/ANNOTATIONS.md`. The state file
   outranks the shared `HANDOFF.md` for this lane and carries the current
   order of work — take the sequence from there.

**Mission (durable):** design Posts, close the open forks with the operator,
and only then build — the build PORTS `activity-registry.js`
(`checkRegistry()` stays at 0 gaps). Mockups: one hand, mockup law in full.
Nothing is built before the design is reacted to.

**Fences:** the nine held screens belong to `work/screens-round4`; the flows
canvas belongs to `work/flows-canvas`. Report, don't fix.