What problem does it solve? Multi-client projects often blur the line between shared platform code and per-client customizations, leading to hardcoded client checks, config files that replace instead of merge, and scattered client code that makes adding new clients painful and risky. ## Core Features & Use Cases - Boundary Audit: Scans the codebase to map core vs client code, detects hardcoded client identifiers, config replacement anti-patterns, scattered client files, migration number conflicts, and missing extension points, then produces a violation report with severity ratings and a health score. - FORK.md Documentation: Generates a FORK.md file documenting the architecture, migration numbering ranges, config merge pattern, and steps for adding a new client. - Refactoring Plan: Produces concrete refactoring steps and scripts to move client code out of core, replace client checks with feature flags, and implement config merging. - Use Case: Before onboarding a second or third client to a SaaS project, run the audit to find every if (client === 'acme') check in shared code and get a prioritized plan to convert them into config-driven feature flags. ## Quick Start Ask the agent to run a fork discipline audit on this project and report where the core/client boundary is violated.
