Athar

Prompt: You are an expert open-source release engineer. Audit and upgrade this repository to be launch-ready following the strict Settl 16-Point Open-Source Standard. Do not truncate, delete, or replace existing architectural manuals, runbooks, or deep context. Preserve all technical depth while executing the checklist below. Checklist & Rules: 1. Hero Visual: Create or ensure a crisp, high-resolution aesthetic vector SVG or PNG banner exists under assets/images/banner.svg (1200x400, dark palette, subtle gradient glow, domain-specific schematics). Avoid GIFs. 2. Top Structure (<8 lines): # Project Name > Plain-words one-line summary (<120 chars, what it does and for whom). <one-command-clone-install-or-run> !Banner 3. One-Command Quickstart: Single copy-paste command right below the one-liner with zero pre-requisite paragraphs. 4. Badges: Add centered shields.io badges matching the tech stack, license, passing CI status, and 24h SLA. 5. Permissive License: Ensure LICENSE (MIT or Apache-2.0) exists in root. 6. Permissive Discovery Topics: Output 8-10 high-traffic GitHub discovery topics and the exact repo About one-liner to set in GitHub repository settings. 7. CI Pipeline: Ensure .github/workflows/ci.yml runs automated tests and linting. 8. Clean History: Verify no .env files, credentials, or private API keys are tracked in git. 9. Good First Issues: Define 3-5 beginner-friendly starter issues under docs/good-first-issues.md with scope, file paths, and acceptance criteria. 10. Community Files: Ensure CONTRIBUTING.md exists with local dev setup, test commands, PR flow, and maintainer SLA. 11. Issue Templates: Add .github/ISSUE_TEMPLATE/bug_report.yml and feature_request.yml. 12. Release Tag: Prepare a v1.0.0 release note and semantic tag changelog. 13. Show HN Draft: Write a draft for Hacker News following HN rules (Format: "Show HN: Name - Plain description", focus on architecture, performance, and trade-offs). 14. 24h SLA: Add an explicit 24-hour maintainer response SLA statement. 15. Scroll Length Optimization: If README is >7,500 chars, collapse deep reference tables, endpoint schemas, and runbooks into <details><summary><b>Expand [Section] Details</b></summary>...</details> drawers to trim visual height by ~30%. 16. Strict Typography: Use zero emojis and zero em dashes throughout all documentation, commits, and issue templates. Use hyphens or colons only. Perform the audit, make the file changes directly, and summarize the before/after scorecard.

Here's my discord link btw: discord.gg/NzzFKfXrt5