workspace-sync

To sync profile templates with team repositories and member workspaces, run a full-sync operation to apply profile changes, execute agent tag filtering, rename context.md to CLAUDE.md, render placeholders, and commit approved updates across all hired members.

Diagnosing submodule discrepancies and workspace drift requires checking submodule branch and merge states, validating symlinks, verifying required files, and surfacing cross-workspace differences to provide actionable fixes like switching to main or resolving conflicts.

Workspace propagation works by pulling team repository updates, running team sync to copy files, rebuilding symlinks, and verifying that individual workspace files match the team sources across all hired members.

Yes, you can preview diffs before applying profile changes to team repositories. The process diffs the profile source against the team repository, performs agent tag filtering, and renders member placeholders to surface changes for operator approval before committing.

Workspace files not matching team sources after a sync may result from invalid symlinks, detached submodule branches, or unresolved merge conflicts. Diagnose cross-workspace drift and verify submodule states to resolve these discrepancies.

Yes, workspace sync handles context.md renames to CLAUDE.md and renders member placeholders for new files automatically during the profile application process to ensure team repositories remain consistent.