Refs: Phase 0.h.
CodeTwin adopts the tooling foundation from
carlosferreyra/rust-template at 62488bc.
This is an in-place migration. Existing source, product crates, release integration, and the
untracked product context are preserved.
tools/xtask, .cargo/config.toml, and workspace metadata identifying codetwin as
the primary crate and product prefix.The action registry records stable release tags resolved during migration. New automation
dependencies are cargo_metadata 0.23.1 and toml_edit 0.25.17; the existing workspace Clap
dependency is shared with xtask. These dependencies belong to development automation, not the
CodeTwin executable. Existing product dependency requirements are preserved.
expect, matching the existing rule
against panicking outside tests and startup.Generator hooks, placeholder manifests, template test scripts, and starter application code are not copied into CodeTwin. Full CI, dependency-policy checks, audit schedules, and Dependabot remain optional.
At the migration baseline, the crates.io packaging failure was: the published binary depends on private,
path-only codetwin-legacy. Resolving the dependency’s publication policy belongs to the
product-crate and release design, rather than this tooling migration. No release workflows,
release scripts, wrapper versions, or publication settings are changed here.
Current consolidation note: codetwin now also depends directly on private, path-only
codetwin-ir, which is the first missing-version error reported by packaging. Both internal
product dependencies need a publication policy before crates.io packaging can work.
Wrapper metadata loading was adapted to the workspace during consolidation; no packages
were published and crate publication settings remain unchanged.
Validate the migration with cargo xtask ci, the ignored generation integration test, and a
release build. Xtask integration tests exercise member-directory discovery, dry-run preservation,
idempotent scaffolds, conflict rejection without partial writes, action substitution, and the
versioned primary CLI scaffold.
Verified during migration:
cargo xtask ci. The Mermaid regression test preserves output bytes and edge styles.cargo build --workspace --release --locked and executable smoke checks.cargo +1.93.0 check --workspace --all-targets --locked with an isolated target directory.