chore: organize repository by subsystem#797
Draft
FuJacob wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Organizes the production and test trees by subsystem, consolidates repository tooling, removes stale generated state, and refreshes the public architecture/privacy documentation. This gives maintainers a navigable ownership map without changing product behavior.
Validation
swiftlint lint --quiet— exit 0xcodegen generate— project regenerated successfullyxcodebuild -project Cotabby.xcodeproj -scheme Cotabby -destination 'platform=macOS' build-for-testing -derivedDataPath build/DerivedData— TEST BUILD SUCCEEDEDLinked issues
None.
Risk / rollout notes
The committed Xcode project changes are generated from the unchanged recursive source declarations in
project.yml. Almost all Swift changes are pure file moves; the only test behavior adjustment makes the llama eval artifact path independent of source nesting depth. This PR intentionally precedes the decomposition and behavioral refactor layers.