Clean up Local-TTS-Studio: fix ARCHITECTURE.md stale references

[Copilot]

Repository cleanup for discoverability and accuracy on an AI-focused profile.

Changes

• ARCHITECTURE.md: Corrected stale project root name (TTS-opensource-app/ → Local-TTS-Studio/) and expanded the services/ directory listing to reflect all current modules (podcast_service.py, podcast_models.py, music_service.py)

No-op (already production-quality)

• README.md — comprehensive: badges, features, architecture diagram, quick-start, API reference, troubleshooting, license
• .gitignore — covers __pycache__, venv/, .env, audio outputs (*.wav, *.mp3), model weights (*.pt, *.bin, *.safetensors), models/, IDE/OS noise

Action required post-merge

Add repository topics via GitHub → Settings → Topics (cannot be set via committed files):

text-to-speech  tts  local-ai  python  ai  speech-synthesis
generative-ai   qwen3-tts  voice-cloning  fastapi  multilingual
offline  huggingface  podcast

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/graphql
  • Triggering command: /usr/bin/gh gh repo view sammy995/Local-TTS-Studio --json repositoryTopics s,HttpsUpgrades,LensOverlay,MediaRouter,PaintHolding,ThirdPartyStoragePartition (http block)
• https://api.github.com/repos/sammy995/Local-TTS-Studio/topics
  • Triggering command: /usr/bin/curl curl -s -H Authorization: token ****** -H Accept: application/vnd.github.mercy-preview+json REDACTED (http block)
  • Triggering command: /usr/bin/gh gh api repos/sammy995/Local-TTS-Studio/topics (http block)
  • Triggering command: /usr/bin/gh gh api -X PUT /repos/sammy995/Local-TTS-Studio/topics -f names[]=text-to-speech -f names[]=tts (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Clean Up and Tag the Local-TTS-Studio Repository

Goal

Make the Local-TTS-Studio repository clean, professional, and discoverable for an AI-focused GitHub profile.

Tasks

1. Add/Update Repository Topics (Tags)

Inspect the actual files in the repo and add relevant topics such as:

• text-to-speech
• tts
• local-ai
• python
• ai
• speech-synthesis
• generative-ai
• coqui-tts / pyttsx3 / bark / tortoise-tts (based on actual library used)
• Any other relevant tags based on actual content

2. Clean Up the README

• If no README exists, create a professional README.md.
• If a README exists, improve it to include:
  • A clear title and description of what the project does
  • What TTS engine/model is used — infer from actual files
  • Features (voice selection, speed control, output formats, etc.) — infer from actual files
  • Tech stack / dependencies — infer from actual files
  • How to install and run the project
  • A clean file structure section
  • Badges (e.g., Python version, license if applicable)

3. General Cleanup

• Add a .gitignore if one doesn't exist (for Python: ignore __pycache__, .ipynb_checkpoints, *.pyc, venv/, .env, audio output files like *.wav, *.mp3, model weights, etc.)
• Note any obvious junk or large binary files in the PR description.

Notes

• Infer all specifics by reading the actual files in the repository before making changes.
• Keep changes minimal and professional.

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: which are basic repos that I can make private. I am trying to build Github profile focused on AI

Assistant: Here's a breakdown of your public repos, sorted into keep public (strong AI/ML signal) vs. safe to make private (generic/non-AI):

---

✅ Keep Public — Strong AI Profile Signal

These directly support an AI/ML-focused profile:

Repo	Why Keep It
Local-TTS-Studio	Local AI / TTS — very relevant
Local-LLM-Arena	Local LLMs — highly relevant
green-agent-agentxbeat	AI agent work
PDFQuery-VectorDB	RAG / Vector DB — trending AI topic
CelebSearch-langchain-OpenAI	LangChain + OpenAI — great showcase
DeepLearning-Basics	Foundational AI — decent
ML-algorithms	Core ML — decent
Movie-Recommender-System	Applied ML project
LoanStatusPredictor	Applied ML project
SMS-spam-classifier	Applied ML/NLP
Banknote-predictor-api	ML + API deployment
BHP-Lregression	ML project (borderline, but fine)
Machine_Learning_Project	ML — keep if it's a solid project
Dynamic-color-detector-opencv	Computer Vision — relevant to AI
OpenCV-Basics	CV basics — borderline, keep if it looks polished
Exploratory-Data-Analysis	Data science foundation

---

🔒 Make Private — Not AI-Relevant

These add noise to an AI-focused profile:

Repo	Reason
web-app-todo	Generic web app
to-do-app	Duplicate/generic web app
api-email-newsletter	Non-AI backend project
cc-collection-leaderboard	Unrelated to AI
Python-Basics	Too basic for a serious AI profile

---

💡 Tips for Your AI Profile

1. Pin your top 6 — Pin Local-LLM-Arena, Local-TTS-Studio, PDFQuery-VectorDB, CelebSearch-langchain-OpenAI, green-agent-agentxbeat, and one applied ML project.
2. Add READMEs — Make sure each pinned repo has a clear README with what it does, tech stack, and a demo/screenshot.
3. Add topics/tags — Tag repos with llm, langchain, ai, machine-learning, etc. for discoverability.
4. Profile README — Create a sammy995/sammy995 repo with a profile README summarizing your AI focus.

User: make repo clean and tag with appropriate tags

Assistant: We're waiting for your response to the tool confirmation dialog to continue with cleaning up and tagging the **DeepLearni...

This pull request was created from Copilot chat.