docs(awesome): add Meows Shop to Commerce

[MrMe0ws]

Adds Meows Shop to the Commerce section.

Meows Shop is an independently developed fork of Jolymmiels/remnawave-telegram-shop, AGPL-3.0, actively maintained. Compared to upstream it adds a full web cabinet (browser + PWA + Telegram Mini App) with its own admin panel, a loyalty program with XP levels, HWID device slots with connect-by-QR invites, an in-cabinet support chat, lifecycle notifications with win-back promo codes, a fortune wheel, a public landing page, and an interactive installer plus a migration tool from Bedolaga.

Requirements:

• Open source (AGPL-3.0)
• Related to Remnawave (sells and manages Remnawave subscriptions via the panel API)
• Target branch: main

Files:

• docs/awesome-remnawave.mdx — import + ProjectCard at the end of the Commerce section
• docs/awesome-remnawave/_install-guides/meows-shop.md — features and install commands for the "Features & More Info" section
• static/awesome/meows-shop.webp — card image (1792×1008, 62 KB)

npm run build passes locally with no new warnings or broken links.

[greptile-apps]

Greptile Summary

Adds Meows Shop to the Commerce catalog with a project card, feature and operational guide, and WebP artwork.

• Imports and renders the new guide in the Awesome Remnawave page.
• Documents features, requirements, installation, updates, migration, and version compatibility.
• Adds the project card image under the static Awesome assets.

Confidence Score: 4/5

The operational guide should be corrected before merging because its update and migration commands fail or can target the wrong Compose project when run outside the installation directory.

The new card wiring is consistent, but the guide documents directory-relative lifecycle commands without first entering the stated installation directory and also executes mutable third-party content directly.

Files Needing Attention: docs/awesome-remnawave/_install-guides/meows-shop.md

Security Review

The Quick Start streams an installer from a mutable third-party branch directly into Bash without pinning or integrity verification.

Important Files Changed

Filename	Overview
docs/awesome-remnawave.mdx	Adds a correctly wired Commerce ProjectCard and guide import for Meows Shop.
docs/awesome-remnawave/_install-guides/meows-shop.md	Adds extensive setup guidance, but later operational commands depend on an unstated working directory and Quick Start directly executes an unpinned remote script.
static/awesome/meows-shop.webp	Adds the image referenced by the new project card.

_{Reviews (1): Last reviewed commit: "docs(awesome): add Meows Shop to Commerc..." | Re-trigger Greptile}

[greptile-apps]

Commands Miss Deployment Directory

When an operator uses Quick Start and later runs these commands from their normal shell directory, Docker Compose fails or targets another project; the migration command at line 54 likewise cannot locate its relative script. Enter /opt/remnawave-telegram-shop before documenting these lifecycle commands.

Knowledge Base Used:

• Environment configuration
• Operations and recovery

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

Installer Executes Mutable Content

This command passes content from the mutable third-party main branch directly to Bash without an immutable revision, integrity check, or review step. Pin or authenticate the installer so later upstream changes cannot silently execute with the operator's shell privileges.

How this was verified: The documented curl response is consumed directly by Bash from a main-branch URL with no checksum or pinned revision.

Knowledge Base Used: Panel deployment