# Tooling Status

High-level support map for wider team adoption.

## Supported Primary Entry Points

- `bytelyst-cli.sh`
- `remove_user_interactive.sh`
- `remove_user_guided.sh`
- `remove_user_from_repos.sh`
- `git-work-safety-tools/`
- `scripts/ubuntu-vm-security-update.sh`
- `scripts/open-notebook-pilot/` + `deployments/open-notebook-pilot/` for the private localhost-only Open Notebook pilot

These are the main starting points the team should discover first.

## Specialized But Self-Contained

- `github_access_scripts/`
- `github_repo_scanners/`
- `Slack Message/`
- `youtube/`
- `supabase monitor/`

These are useful, but they have narrower scopes or their own setup/runtime assumptions.

## Legacy Or One-Off Surface Area

- many root-level `list_*.sh` scripts
- account-specific helper scripts such as `remove_user_i-ayushh18.sh`
- operational snapshot JSON files in the repo root

These may still be valuable, but they are not the best onboarding path for new teammates. Prefer documenting and linking to the supported entry points above.

## Team-Readiness Guidance

Before broad internal rollout:

- do not keep live credentials in tracked files
- do not keep generated outputs in git unless they are intentional fixtures
- prefer templates such as `accounts.example.json` and `.env.example`
- add new standalone scripts under `scripts/`
