Repository navigation
Conversation
|
Important Pre-merge checks failedPlease resolve all errors before merging. Addressing warnings is optional.
Full details: Public Resource Access
Full details: Change Map Design Review
Full details: Pr Size
|
UI Review (
|
Change mapThe requested change is a physical repository reorganization. The previous root mixed Studio implementation, engine projects and development infrastructure. The stopping condition is a navigable four-area root with updated build/test/deployment consumers and preserved runtime interfaces. Design and validation · Exact old/new directory mapping
The remaining component trees are relocated using the exact mapping in the manifest: Studio under This comment is a review index, not a claim that the current automated per-file coverage gate passes. GitHub truncates its PR-files API at 3,000 files. This migration exceeds that limit and requires accommodation in that existing automation before readiness. Obtain the complete per-file inventory locally: git fetch origin main codex/repository-layout
git diff -M -l20000 --name-status eb4745537a50fbb9fee1246ce795fee2389be82e origin/codex/repository-layoutThe design records passing builds, isolated artifact imports and focused test results, plus the 12 pre-existing Faiss mock failures reproduced on the base revision. Release/platform/cloud and deployment validation remain pending. Adding model-family APIs, extracting GNN internals, changing contribution policy and migrating external SDM repositories are outside this PR. |
UI Test Jobs Completed on 6aaf625 |
|
This means the UI client code needs to be regenerated. To regenerate the UI client code in this PR, comment: |
Fixes #358
This moves the repository to four main areas:
apps/,packages/,development/anddocs/. Studio owns its backend, frontend and deployment assets; reusable engine projects are grouped by responsibility. Component internals and Python distribution/import names stay intact.System design and validation record · Exact directory move manifest
Maintained change-map comment
Implementation
apps/studio; make the root Python manifest a virtual workspace and update all workspace locations.kumo.pytorchAPI at its existingpackages/experimental/kumo-pytorchlocation;models/is for model artifacts and adapters.development/config; retain small root command entry points and wire explicit configuration into local commands and CI.packages/engine-bundle.txt; keep the existing native DiskGraph build separate.dev layout-checkand a CI check for project locations, bundle inputs, local npm dependencies, symlinks and Docker ignore consistency.Validation
The local merged wheel uses
--no-zigandMAX_GLIBC=2.35for this host; it is a validation artifact. Release CI retains its existing Zig/default portability settings.Review and remaining validation
This is deliberately a draft. Follow-up commits through
5302e0564address CI path, formatting, generated-notice and package-configuration failures; CI is rerunning. The complete remote SDK pre-commit suite also passes locally, along with the public-reference scanner’s 63 tests. The full release/platform/cloud/deployment matrix still needs CI and owner review. The engine's computational runtime AST is unchanged apart from the source location of the skill packager; model/index formats are preserved.GitHub's files API truncates at 3,000 files, while this migration moves about 8,000. The existing per-file change-map automation therefore cannot validate the entire migration. Use the committed move manifest and full local Git diff; this automation limitation needs accommodation before marking the PR ready. A maintained change-map comment links the review areas and validation record.