[gold-silver-copper]

• prune finds sets only through records in the workspace's repos and keeps a set with any foreign member; remove refuses another workspace's set (also with --force), names that workspace, and lists parts of the workspace it couldn't read.
• Run from inside a set, worktree commands (create, list, remove, prune) find sets where the checkout the set stands for keeps them; a set created there records that checkout as its project, and its .gitignore entry goes there.
• create and add place each repo at its path from the meta config (as --recursive already did), so a set mirrors the workspace layout; a plan has one worktree per place (one branch each; a conflict is refused), parents (derived from places, found by path) first; add compares places as paths (Windows separators); worktree exec --include takes project names, also in a set without its root.
• add dedupes by place too (a repo given by name and by path is one worktree; on two branches it is refused before git runs). add also compares real destinations, so a member behind a link is found before git runs, and refuses a place that already holds something (a nested repo already in the set, or files in the way, named as such). Automatic parents come only from the workspace's projects (looked up through only the configs on the parent's path), so a set never holds a repo remove would call foreign and a broken unrelated nested config doesn't stop create. worktree exec takes names through set_config and repo_names, reading configs only with a filter.
• Hooks read the workspace's config (owner_dir) and run in its directory, worked out before anything is deleted, so remove/prune run from inside the set they delete still fire post-destroy/post-prune.
• Skipped parents print a visible warning; the dry run notes a project at a link; --no-deps help says a nested repo still gets its parent project.
• meta git clone escapes the URL it echoes.
• create --all --recursive covers every nested level; add doesn't print ✓ Added before a failed record write; a bad --ttl gives one error; prune lists a kept set once.
• Unknown subcommands, recursive alias errors, rejected commit-ish/--meta/--from-pr values, the PR branch, the dry-run preview, prune's kept names and clap errors are escaped (clap errors via meta_cli::args::escaped_error).
• The "orphaned (all source repos removed from project)" prune reason is gone: such a set is no longer the workspace's (see the root PR).

Part of the meta stability set: gitkb/meta#128 has the full description and how it was verified. Merge together with it (same branch name, so CI builds them together).

Implements [[tasks/harmony-2793]]

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: fdfd1e98-1a04-4569-92e2-015a83a2ea97

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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