Skip to content

Resync the vendored backend types - #241

Merged
max-tet merged 1 commit into
mainfrom
chore/clayde/resync-backend-types
Sep 28, 2026
Merged

max-tet merged 1 commit into
mainfrom
chore/clayde/resync-backend-types

Conversation

@ClaydeCode

Copy link
Copy Markdown
Contributor

What

Regenerates shard_core/data_model/backend from freeshard-controller main (0ec6c6a).

Why now

The drift-check job compares this directory against controller main byte for byte, and
it is currently red on every PR opened against main — #173 and #240 both fail it.
#180 and #181 show green only because their runs predate the drift. So this is not one
branch's problem; it blocks anything opened today.

What changed

Entirely the controller's shard-migration work, which is already deployed on the
controller side and simply was never regenerated here:

Change File
Permission.MIGRATE_SHARD permission_model.py
ShardStatus.CUTTING_OVER shard_model.py
cloud on ShardUpdateDb shard_model.py
new ShardMigration* models, statuses and exceptions shard_migration_model.py (new)

Verification

  • Generated by just get-types, not hand-edited.
  • Purely additive: three insertions plus one new file, nothing removed or renamed.
  • ruff check clean; the new module imports cleanly and both new enum members resolve.
  • Nothing in shard_core imports shard_migration_model, and no code matches
    Permission or ShardStatus exhaustively, so the added members change no behaviour.
    The only consumer of ShardStatus outside the vendored dir is tests/conftest.py,
    which pins ASSIGNED.

Full suite not run locally for this one — it is generated vendored types with no importers;
CI covers it.

🤖 Generated with Claude Code

The drift gate compares shard_core/data_model/backend against
freeshard-controller main byte for byte, and it is red on every PR opened
against current main (#173 and #240 both fail it; older PRs show green only
because their runs predate the drift).

The whole of the difference is the controller's shard-migration work, which
is already deployed on the controller side and simply never regenerated
here: Permission.MIGRATE_SHARD, ShardStatus.CUTTING_OVER, the cloud field on
ShardUpdateDb, and the new shard_migration_model module.

Generated by `just get-types` against controller main 0ec6c6a. Purely
additive, nothing is removed, and no shard_core module imports
shard_migration_model — this only satisfies the gate.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@max-tet
max-tet merged commit 950b3c8 into main Sep 28, 2026
9 of 10 checks passed
@max-tet
max-tet deleted the chore/clayde/resync-backend-types branch September 28, 2026 12:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants