SMOODEV-1787: consume published smooth-operator-core; delete in-tree copy (PR 1/4)#92
Merged
Merged
Conversation
…te the in-tree crates/smooth-operator copy (PR 1/4: dual-engine collapse, no functional change) The in-tree engine (smooai-smooth-operator) and the public smooth-operator-core (smooai-smooth-operator-core) were the same engine but had diverged. The only differences were the public core's dormant `bigsmooth`-feature gating of the BigSmooth reporter (with a no-op stub when disabled) plus cosmetic public-sanitization edits. smooth never enables the `bigsmooth` feature and never sets a reporter, so the gated reporter calls were dormant no-ops — the cutover loses nothing. Repoint the workspace `smooth-operator` dep to the published `smooai-smooth-operator-core` (rev-pinned git dep), package-aliased so the ~12 consumers' `use smooth_operator::…` imports compile unchanged. Convert the two crate-level path-dep overrides (smooth-bigsmooth, smooth-operative) to `smooth-operator.workspace = true`. Delete crates/smooth-operator/. Git dep (not a sibling path dep) to avoid the CI `cargo metadata` failure SMOODEV-1464 hit with a `../`-style path dep. No functional change, no module removal — later PRs. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: 0dfa72b The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
Problem
PR 1 of 4 in the program to decouple the `th code` coding harness from the public agent engine.
`smooth` was building against an in-tree copy of the agent engine at `crates/smooth-operator` (`smooai-smooth-operator`), which had diverged from the published public engine `smooai-smooth-operator-core` (`github.com/SmooAI/smooth-operator-core`). Two copies of the same engine is the root problem this program removes.
Solution
`smooth` now consumes the published `smooth-operator-core` engine; the in-tree copy is deleted. The ~12 consumers compile unchanged — this is the dual-engine collapse only. No functional change, no module removal (that lands in later PRs).
Divergence analysis (full diff of both `src/` trees + Cargo.toml)
The two engines differed in only two ways, neither of which smooth depends on:
No port into the core was needed — there was no in-tree-only code that smooth's consumers use and the public core lacks.
Wiring
`smooth-operator = { git = "https://github.com/SmooAI/smooth-operator-core.git", rev = "bb9a256…", package = "smooai-smooth-operator-core" }`
Verification (real output)
🤖 Generated with Claude Code