Skip to content

consolidation: R1 — decide opensin-ai-cli merge vs split #1116

@Delqhi

Description

@Delqhi

Consolidation ticket R1 — opensin-ai-cli vs OpenSIN-Code

Tracker: OpenSIN-overview/docs/FOLLOWUPS.md § R1

Co-owner: Team-SIN-Code-Core.

Problem

Two Rust coding CLIs in the same org:

  • OpenSIN-AI/opensin-ai-cli — 70 files / 34.6k lines / 9 crates
  • OpenSIN-AI/OpenSIN-Code — canonical autonomous TS CLI, also ships a Rust engine (71 files / 37.7k lines)

Currently nothing prevents a new contributor from landing Rust work in the wrong repo.

Decision required

  1. Merge the useful crates of opensin-ai-cli into OpenSIN-Code/crates/* and archive opensin-ai-cli with a redirect README, OR
  2. Split responsibilities — e.g. OpenSIN-Code = TS frontend + orchestration, opensin-ai-cli = Rust engine only. Document the split in OpenSIN-overview/docs/CANONICAL-REPOS.md and remove the rationalization flag.

Acceptance criteria

  • Crate-by-crate comparison matrix in docs/consolidation/R1-diff.md
  • Written decision with rationale (performance, runtime model, user-facing surface)
  • If merge: migration PR(s) landing the useful crates into OpenSIN-Code/crates/*
  • If split: updated CANONICAL-REPOS.md declaring both as canonical with non-overlapping roles; flag removed
  • OpenSIN-overview/docs/FOLLOWUPS.md § R1 status changed to DONE
  • Companion README-banner issue on opensin-ai-cli closed

Unblocks

Sprint 1 heartbeat work in opensin-ai-agent-feature-spec.md § 2.1.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions