Skip to content

Design migration tooling after read-only analysis is reliable #4

Closed

Description

@Zach677

Context

Modern.UIKit should not promise automatic migration until read-only analysis is reliable across enough real repo shapes.

Scope

Define the first supported migration slice after analysis gates are strong enough. Candidate directions:

  • SwiftUI entry wrapped by a UIKit shell
  • Tuist workflow hardening without replacing Tuist
  • UIKit/Xcode additive baseline completion
  • documentation-only adoption for repos that should preserve their existing architecture

Acceptance

  • Migration tooling has a narrow write scope.
  • Every write path is guarded by can_apply or an equivalent explicit capability.
  • Existing source of truth, signing, bundle identifiers, remotes, and product source are preserved by default.
  • The feature has real fixture coverage before being advertised in README.

Activity

  1. linear-code commented on May 20, 2026

    @linear-code
  2. Zach677 commented on Jun 12, 2026

    @Zach677
    OwnerAuthor

    Parking this intentionally: the first migration slice should be shaped by a real repository that needs the migration, after #1 and #3 prove the read-only analysis reliable. No design work until that trigger fires.

  3. Zach677 commented on Jul 18, 2026

    @Zach677
    OwnerAuthor

    Implemented the first write-enabled slice as guarded, additive baseline completion for clean single-project UIKit repositories. The pinned AtesiT/justPracticeOnUIKITWithoutStoryboard@f59beba smoke created exactly 11 declared files, preserved HEAD, remotes, and tracked files, kept DerivedData out of the worktree, and passed mise build; CI is green: https://github.com/Zach677/Modern.UIKit/actions/runs/29645034847

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions