refactor(engine): rename package to phase-engine - #6739
Merged
Conversation
The package rename leaves every documented `cargo <verb> -p engine` invocation pointing at a package that no longer exists. Retarget the ones that are live instructions — skills, agents, workflow scripts, CLAUDE.md, the contributor guide. Historical plan records under `.claude/wf/` are left alone: they describe commands that were run at the time, and rewriting them would falsify the record. Doc comments inside `crates/engine/src/` are also untouched, to keep this commit free of any .rs edit.
matthewevans
enabled auto-merge
July 28, 2026 19:42
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThe Rust engine package is renamed from ChangesEngine package migration
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested labels: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Preserve the package rename while retaining main’s Manabrew Protocol v3 dependency and AGPL leaf licensing. Co-authored-by: matthewevans <matthewevans@users.noreply.github.com>
Parse changes introduced by this PR✓ No card-parse changes detected. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Renames the
enginepackage tophase-engineso an external consumer (ManaBrew) can name it unambiguously in a git dependency:engineis too generic to appear in a third party's manifest, and the name is squatted on crates.io at 0.0.0.Zero source changes
There are 17,414
engine::references across 1,573 files. None of them change. Cargo takes the extern crate name from the dependency key, sopackage = "phase-engine"renames the package while every dependent keeps sayingengine:[lib] name = "engine"keeps the produced artifact and extern name stable.git diff --name-onlycontains no.rsfile.Not publishing
crates.io publication was investigated and rejected: the packaged crate is 19.3 MiB compressed — 11 MiB even after excluding every test and snapshot — against a 10 MiB limit. Distribution is by git dependency, so no
include/excludekeys were added and no publish step exists.Beyond the workspace
lobby-worker/broker-wasmisexcluded from the root workspace and keeps its own lockfile, socargo check --workspacecannot see it. Its lock and thecargo update --package engineinnightly-release.ymlare both updated here; left alone, the nightly release job would have failed days later with an unmatched package-ID spec.--features engine/proptestin.githooks/pre-pushand.cargo/config.tomlis correct as-is and deliberately unchanged — cargo's CLIpkg/featsyntax resolves through the dependency key. Verified against a non-vacuous probe:Docs
The second commit retargets
cargo <verb> -p enginein live instructions (skills, agents, workflow scripts, CLAUDE.md, contributor guide). Historical plan records under.claude/wf/are left alone — they describe commands run at the time. Doc comments insidecrates/engine/src/are untouched to keep the diff free of.rsedits.Verification
cargo fmt --allcargo check --workspace --all-targetscargo test -p phase-enginecargo clippy --workspace -- -D warningsNon-vacuity check, since a no-op edit would also pass every gate:
phase-enginepresent, bareengineabsent.Summary by CodeRabbit
phase-engineand updated related crate wiring to keep the same library interface in place.phase-engineinstead of the old package name.phase-engine.