Summary
There is no manifest format (.cdidx-workspace.yml / cdidx.workspace.json / similar) for declaring monorepo or multi-repo workspace topology. A user with a monorepo containing 12 sibling projects, or a workspace of 4 sibling repos that should share one logical index, has to manually pass --db paths and re-discover topology on every invocation. There's no equivalent of Cargo workspaces, npm workspaces, Go workspaces, or .sln.
Where
src/CodeIndex/Cli/DbPathResolver.cs:19-50 (single-DB resolution; no manifest discovery)- No
WorkspaceManifest model exists
Suggested approach
(1) Define a .cdidx-workspace.yml schema with: members (list of repo paths or globs), index_strategy (one DB per member vs single shared DB), default_db_name, shared_ignores. (2) Have DbPathResolver walk parent directories looking for the manifest, then resolve --db relative to the manifest's index_strategy. (3) Add cdidx workspace list / workspace status subcommands that report each member's index health. (4) Document in DEVELOPER_GUIDE under a new "Workspaces" section. (5) Add a sample manifest under examples/. (6) Coordinate with #C305 (per-workspace config) and #C306 (cross-DB references).
Summary
There is no manifest format (
.cdidx-workspace.yml/cdidx.workspace.json/ similar) for declaring monorepo or multi-repo workspace topology. A user with a monorepo containing 12 sibling projects, or a workspace of 4 sibling repos that should share one logical index, has to manually pass--dbpaths and re-discover topology on every invocation. There's no equivalent of Cargo workspaces, npm workspaces, Go workspaces, or.sln.Where
src/CodeIndex/Cli/DbPathResolver.cs:19-50(single-DB resolution; no manifest discovery)WorkspaceManifestmodel existsSuggested approach
(1) Define a
.cdidx-workspace.ymlschema with:members(list of repo paths or globs),index_strategy(one DB per member vs single shared DB),default_db_name,shared_ignores. (2) HaveDbPathResolverwalk parent directories looking for the manifest, then resolve--dbrelative to the manifest'sindex_strategy. (3) Addcdidx workspace list/workspace statussubcommands that report each member's index health. (4) Document in DEVELOPER_GUIDE under a new "Workspaces" section. (5) Add a sample manifest underexamples/. (6) Coordinate with #C305 (per-workspace config) and #C306 (cross-DB references).