Summary
The codebase still uses forge naming extensively — crate names (forge_domain, forge_app, forge_main, etc.), module prefixes, config paths, and internal references. This should be renamed to graff to match the product name.
Scope
- Crate names:
forge_domain -> graff_domain, forge_app -> graff_app, etc.
- Module prefixes:
ForgeWidget, ForgeApi, etc.
- Config paths: any
forge-prefixed config directories or files
- Internal references: comments, docs, error messages
- Binary names:
forge_main crate already produces graff binary, but the crate name itself is still forge_main
Approach
Large refactor, do in phases:
- Rename crates (Cargo.toml workspace members + all
use paths)
- Rename public types and traits
- Rename config paths and env vars (with migration for existing users)
- Update docs and comments
Summary
The codebase still uses
forgenaming extensively — crate names (forge_domain,forge_app,forge_main, etc.), module prefixes, config paths, and internal references. This should be renamed tograffto match the product name.Scope
forge_domain->graff_domain,forge_app->graff_app, etc.ForgeWidget,ForgeApi, etc.forge-prefixed config directories or filesforge_maincrate already producesgraffbinary, but the crate name itself is stillforge_mainApproach
Large refactor, do in phases:
usepaths)