fix: repair Crucible backend regressions#68
Open
jungdaesuh wants to merge 1 commit into
Open
Conversation
This was referenced Jul 1, 2026
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.
Summary
Fixes confirmed backend correctness regressions from the Crucible review on top of latest
origin/develop.Changes
remote_dirbefore remote shell/rsync use.develop.Tests
uv run ruff format .-> 59 files left unchangeduv run ruff check .-> passeduv run ruff format --check .-> 59 files already formatteduv run ty check src-> passeduv run --extra service pytest -q-> 320 passed, 5 skippedRisk
Medium: touches numerical/data-fetch paths, but each confirmed regression has focused coverage.
Rollback
Revert this PR. No migrations, data writes, or schema changes.