vc:watzup

A read-only repository state summary surfaces the current branch, dirty status, ahead/behind counts, local and remote refs, recent commits, and worktrees. It also exposes active project plans with an advisory selected-plan hint to orient teammates without granting execution authority.

Orienting new contributors requires scanning local git metadata and filesystem plan files to surface active branches, worktrees, recent commits, and advisory plan hints. This read-only snapshot provides full visibility into the repository state and next steps without modifying the working directory.

Yes, the repository state scan enforces read-only behavior across branches, worktrees, and plan files. It only surfaces advisory hints about the selected plan and requires an explicit fetch or selection command before any modifying action is taken.

A git worktree and plan summary works by reading local git metadata and filesystem project plan files to generate a concise snapshot. It captures the detached HEAD or branch state, worktree listings, and advisory selected-plan context so reviewers can quickly understand the current development status.

Yes, local git metadata and filesystem access to plan files are required to generate a repository handoff summary. The scan reads branches, worktrees, recent commits, and project plans directly from the local checkout to produce an accurate, read-only orientation snapshot.

The read-only repository state summary cannot execute plan actions or modify the working tree. It only provides advisory hints about the selected plan and requires an explicit fetch or selection input to perform any state-changing operations beyond orientation.