GitHub Cleanup Plan

This plan is for turning the current local OrganicOS work into a coherent GitHub presence without accidentally publishing private runtime state.

Current State

• Public GitHub has one OrganicOS concept repo and several forks.
• The active implementation work mostly lives locally.
• Several active local trees either have no GitHub remote or still point at upstream projects.
• The local GitHub CLI token is invalid, so authenticated writes are currently blocked.
• Many local trees are dirty and include experimental, backup, or runtime-sensitive material.

Safety Rules

Do not push any OrganicOS tree until it has passed a redaction review.

Watch for:

• tokens and API keys;
• Tailscale hostnames and private endpoints;
• credentials or preserved user state;
• browser/session state;
• Home Assistant secrets;
• Jellyfin/Cockpit/admin URLs;
• local .config data;
• private LAN details;
• WSL handoff artifacts;
• large binaries, build output, generated caches, and node modules.

Phase 1: Inventory and Naming

Goal: decide what each repository is and what story it should tell.

Recommended public names:

Proposed Repo	Purpose	Initial Source
organicos-portal	Local portal and docs site	/home/shane1806481/dev/organicos-portal
organic-glass	Electron shell, panels, launcher, assistant surfaces	/home/shane1806481/dev/organic-glass
organic-os-decoration	KDE shell/theme/window decoration work	/home/shane1806481/dev/organic-os-decoration
input-nebula	Android/input/ADB control surface	/home/shane1806481/dev/input-nebula
moonlight-nebula-filedrop	File-drop service and client docs	/home/shane1806481/dev/moonlight-nebula-filedrop
supernova-integration	Apollo/Supernova local integration notes and packaging	/opt/organic/components/apollo-nebula plus handoff docs
moonlight-nebula	Moonlight client modifications and docs	/home/shane1806481/dev/moonlight-qt-local

Phase 2: Local Repo Hygiene

For each candidate repo:

1. Create a clean branch.
2. Add or repair .gitignore.
3. Remove generated artifacts and private runtime files.
4. Write a minimal README.md.
5. Add license and attribution notes where upstream code is involved.
6. Add a SECURITY.md or redaction note for private-runtime boundaries.
7. Build/test locally.
8. Only then connect a GitHub remote.

Phase 3: GitHub Profile Cleanup

After authentication is fixed:

1. Add repository descriptions.
2. Add topics such as organicos, organic-glass, nebula, plasma, x11, tailscale, moonlight, apollo, home-assistant, and local-ai where accurate.
3. Pin the repos that tell the OrganicOS story.
4. Archive or leave alone old forks that are not part of the story.
5. Keep fork READMEs honest about upstream lineage.

Phase 4: Documentation Publishing

The portal should become the source of truth first. GitHub READMEs should then link back to the relevant portal pages.

Recommended docs to complete before broad public publishing:

• OrganicOS overview;
• evolution map;
• repository map;
• service and port map;
• Organic Glass architecture;
• Nebula/OpenClaw integration;
• Input Nebula guide;
• Supernova/Apollo integration notes;
• security and redaction checklist.

First Concrete Next Step

Re-authenticate GitHub:

gh auth login -h github.com

Then pick one low-risk repo to publish first. The safest first candidate is organicos-portal, because it is already small, builds cleanly, and contains docs rather than private runtime state.