Skip to content

Fix stale Rift parent and workspace name resolution - #114

Merged
dbpolito merged 1 commit into
mainfrom
fix/rift-stale-parent-resolution
Jul 29, 2026
Merged

Fix stale Rift parent and workspace name resolution#114
dbpolito merged 1 commit into
mainfrom
fix/rift-stale-parent-resolution

Conversation

@dbpolito

Copy link
Copy Markdown
Contributor

Ticket

SKIPPED

Description

Prevent stale OpenCode workspace metadata from nesting new Rift workspaces beneath a removed managed parent. Normalize cached Rift paths back to the original checkout and select an available suffixed name before OpenCode registers a workspace, keeping OpenCode and Rift aligned without global registry cleanup.

Checklist

Parent Resolution

  • Normalize cached managed-workspace paths to the original Rift source
  • Register new workspaces beneath the project-level Rift directory

Name Resolution

  • Detect names already present in the Rift registry
  • Select a concise numeric suffix before workspace registration
  • Preserve transactional mismatch rollback

Validation

  • Verify that bun run compile succeeds
  • Confirm that bun run typecheck reports no errors
  • Check that all 82 tests pass with bun run test

- unwrap cached managed-workspace paths to the original checkout
- suffix names that already exist in the Rift registry
- cover stale parent and collision resolution with regression tests
@dbpolito dbpolito self-assigned this Jul 29, 2026
@dbpolito
dbpolito merged commit 05a137d into main Jul 29, 2026
1 check passed
@dbpolito
dbpolito deleted the fix/rift-stale-parent-resolution branch July 29, 2026 13:33
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.

1 participant