Rewrite README with complete plain-text documentation

[Copilot]

The existing README was incomplete — missing a title, installation instructions, and any explanation of how the code works internally. The problem statement requested a concise, plain-text summary covering code logic, usage, applicability, ownership, and a link to the repo owner's GitHub profile.

Changes

• README.md — fully rewritten with the following sections:
  • What It Does — per-tool description of user flow for all three utilities (video downloader, user ID finder, video details lookup)
  • How It Works — internal logic: subprocess + yt-dlp, requests + regex for user ID extraction, json for metadata parsing, colorama/pyfiglet for terminal UI
  • Requirements — explicit pip install commands for all four dependencies
  • How to Use — numbered steps with a worked example for each tool
  • Where to Use It — Linux/macOS/Windows terminal, local only, no server
  • Why Use It — Facebook exposes no public API for these operations; tool automates browser-level actions from the CLI
  • Owner — EIRSVi (script author); shiliaiwei (repo maintainer) with profile link https://github.com/shiliaiwei
  • Disclaimer — educational use, user responsible for ToS compliance

Original prompt

Summary this description and code logical working and into short answer true and no emoji, or link how it working and how to use, where can use and why and how and owner of script and rewrite the read me apply change push to GitHub mention my GitHub user and link it my profile

[Copilot]

Pull request overview

Rewrites the repository README to provide complete, plain-text documentation of the Facebook Tools Suite, including tool behavior, internal logic, requirements, usage examples, applicability, ownership, and disclaimer.

Changes:

• Added clear “What It Does” and “How It Works” sections covering all three utilities.
• Documented installation requirements and step-by-step CLI usage with examples.
• Added platform scope (“Where to Use It”), rationale (“Why Use It”), and explicit ownership/maintainer info.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The example download location uses the Unix-style "~/Videos/" path, but the README also claims Windows support. Consider making the example path platform-neutral (e.g., "your home Videos folder") or include the Windows equivalent (like "%USERPROFILE%\Videos").

Suggested change

	- The downloaded file appears in ~/Videos/
	- The downloaded file appears in the Videos folder in your home directory (for example, ~/Videos/ on Linux/macOS or %USERPROFILE%\Videos on Windows)