Reorganization and cleanup

[gitauto-ai]

Resolves #263

Summary

Reorganize and clean up the project to prepare CoPilot_Experiment_0 and CatCleanup as candidates to replace main.

Changes

• Prioritizes CoPilot_Experiment_0 and CatCleanup as potential successors to main
• Performs initial project structure cleanup and refactoring to support the transition
• Intends no functional changes at this stage
• Notes that further work is required before either can fully replace main

git fetch origin
git checkout gitauto/issue-263-20251224-221333-GebK
git pull origin gitauto/issue-263-20251224-221333-GebK

[metavacua]

/gemini does this pull request in any way use the actual named branches?

[gemini-code-assist]

That's a great question! This pull request doesn't directly perform Git operations on named branches (like merging or creating them). However, it does introduce and plan for two distinct experimental approaches, CoPilot_Experiment_0 and CatCleanup, which are explicitly described in the pull request description and the docs/REORGANIZATION_PLAN.md file as "candidates to replace main".

These are essentially conceptual "named branches" of development that this PR is setting up. The new directories experiments/CoPilot_Experiment_0 and experiments/CatCleanup contain READMEs outlining their respective plans, indicating they are intended to be separate, significant development efforts that could eventually become actual Git branches or replace the main branch.

So, while not manipulating Git branches directly, the PR's core purpose is to establish the framework for these future development paths, which are named and treated as distinct branches of work.

[metavacua]

The pull request should target the named branches and should not be a branch created from main and proposed for merge back to main.
The pull request either as plans or as an actual proposed merge of one of the named branches should include a detailed account of the changes from the current main to the CoPilot_Experiment_0 as well as extrapolation of what further issues and organizational principles need to be documented or implemented to make the candidate branch ready for replacing the main branch. The pull request should call for a review using /gemini as the command starting the pull request code review; the pull request code review should formally argue the case using facts, figures, and metamathematical methods including constructive witnesses within the repository itself either past or in the proposed branch.

The pull request should include detailed instructions for future actions particularly if the pull request is not deemed ready to replace the main branch.