What problem does it solve?
Changing LikeC4 project discovery and config handling is error-prone because document ownership and per-project exclusion are separate concerns, and regressions easily slip into multi-project workspaces, shared include paths, and Windows path matching.
Core Features & Use Cases
- Ownership vs. exclusion discipline: Preserves the distinction between
ownerProjectId(document), isExcluded(projectId, document), and workspace-level exclusion semantics when editing ProjectsManager.ts.
- Regression matrix: Provides a concrete test matrix covering nested projects, sibling prefix collisions, external include paths, shared includes, reload behavior, workspace excludes, and Windows paths.
- Focused verification workflow: Supplies targeted commands for running
ProjectsManager.spec.ts, typechecking, and formatting checks before submitting changes.
- Use Case: When fixing a bug where a file excluded by one project is incorrectly dropped from another project that includes it, follow the workflow to reproduce the scenario, add the matching regression test, and verify workspace-startup scanning behavior.
Quick Start
Ask the assistant to fix a LikeC4 project ownership or exclusion bug using this workflow, starting from ProjectsManager.ts and adding the matching regression test.