Svelte good first issues

AI Summary: This issue proposes adding an explicit explanation of the NOVA classification (or Ultra-processed levels) within the Compare mode of the application. The goal is to help users better understand the labels by providing a concise explanation via a tooltip or help link, with an option to link to more detailed documentation.

AI Summary: This issue requests the addition of the `/api/health` public endpoint to the `static/llms.txt` file, which documents public agent URLs. The change involves adding a single line to the plain text file, excluding any administrative routes. The goal is to ensure all publicly accessible health check endpoints are documented.

AI Summary: This issue proposes adding a loading skeleton to the paste view while content is being fetched and decrypted. The skeleton will display a placeholder for the editor and toolbar, improving the user experience on slower connections by reducing perceived load time and indicating that the application is working. The implementation should also respect the user's preference for reduced motion.

AI Summary: This issue requests the creation of a new documentation file, `docs/deploy-vps.md`, to guide users on deploying the project on a VPS using a reverse proxy. The guide should cover configurations for Nginx or Caddy, along with a process manager.

AI Summary: This issue requests the addition of a new documentation file, `docs/deploy-fly.md`, to guide users on deploying the project to Fly.io. The new documentation should leverage the existing Dockerfile if one is available.

AI Summary: This issue requests the addition of a new documentation file, `docs/deploy-railway.md`, to guide users on deploying the project to Railway. The guide should utilize existing environment variables from `.env.example` and does not require any new code adapters. The work will be verified by checking for the file's existence and a new link in the README.

AI Summary: This issue requests the creation of new documentation pages for self-hosting the project on three different platforms: Railway, Fly.io, and a general VPS using Docker. Each guide should be concise, list necessary environment variables, and will be located in a new `docs/deploy/` directory. The actual Docker setup is out of scope for this issue.

AI Summary: This issue proposes adding a new `completion` subcommand to the CLI tool. This subcommand should generate static shell completion scripts for Bash, Zsh, and Fish shells, and the installation instructions for these completions need to be documented. The goal is to provide users with an easy way to enable command-line autocompletion for the tool.

AI Summary: This issue proposes adding a `--json` output mode to the CLI tool. This mode will provide machine-readable JSON output for both 'create' and 'get' commands on stdout, while errors will be directed to stderr as JSON. The goal is to ensure stdout remains clean for piping to other tools.

AI Summary: This issue proposes adding a 'Clone' button to the paste view. Clicking this button should pre-fill the home editor with the decrypted content of the paste, using `sessionStorage` for a client-side only transfer.

AI Summary: This issue proposes adding a QR code to the share flow after a paste is created. The QR code should encode the full share URL, including the `#key` fragment, and be generated lazily on the client-side using a small, lazy-loaded library. The implementation should maintain the same client-side trust model as the existing key-in-URL functionality.

AI Summary: This issue proposes adding server-side validation for the `language` and `salt` parameters in the `POST /api/paste` endpoint. The `language` should match a specific regular expression, and `salt` must be a base64 string not exceeding 64 characters. Invalid inputs should result in a 400 Bad Request response, and tests should be added to cover these scenarios.

AI Summary: This issue proposes to optimize the home page by lazily loading editor themes instead of statically importing all of them. This will involve using dynamic imports to load themes only when they are selected, improving initial page load performance. The goal is to ensure themes are not included in the main entry chunk and that theme switching functionality remains unaffected.

AI Summary: This issue requests an audit of public Svelte templates to ensure proper semantic HTML structure. The goal is to improve accessibility and SEO by verifying landmark regions, single H1 per page, logical heading order, and meaningful link text. The acceptance criteria focus on avoiding skipped heading levels and ensuring main, nav, and footer landmarks are present.

AI Summary: This issue aims to improve the usage of `$effect` and `$effect.pre` within the codebase. It involves reviewing existing code for common anti-patterns like unnecessary subscriptions or missing cleanup, and identifying work that could be better handled by `$derived`. The resolution includes updating documentation and fixing any identified misuse in performance-critical areas.

AI Summary: This issue proposes adding a `.devcontainer` configuration to simplify the development setup for new contributors. It aims to automate the installation of Node.js, pnpm, and environment variable setup, allowing for a one-click setup in GitHub Codespaces or VS Code. The goal is to enable a working development environment within two minutes, including an optional MongoDB sidecar for testing.

AI Summary: This issue proposes adding structured request logging to the server, outputting logs in JSON or key=value format. The logs should include details like method, path, status, and duration, while also redacting sensitive information and request bodies. The goal is to have a single, production-friendly log line per request, ensuring request IDs are propagated and no PII or ciphertext appears in the logs.

AI Summary: This issue proposes integrating Renovate, an automated dependency management tool, to streamline the process of updating project dependencies. The goal is to automatically create pull requests for patch and minor updates weekly, and for major updates monthly, while keeping specific key dependencies on their current tracks. The setup requires configuring Renovate with specific rules and documenting the workflow.

AI Summary: This issue requests the creation of a new documentation file, `docs/deploy-vps.md`, to guide users on deploying the project on a VPS using a reverse proxy like Nginx or Caddy, along with a process manager. The goal is to provide clear deployment instructions for this specific scenario.

AI Summary: This issue requests the addition of a new documentation file, `docs/deploy-fly.md`, to guide users on deploying the project to Fly.io. The existing Dockerfile should be reused if one is available.

AI Summary: This issue requests the addition of a new documentation file, `docs/deploy-railway.md`, to guide users on deploying the project to Railway. The guide should leverage existing environment variables found in `.env.example` and does not require any new code adapters. The work involves creating the file and adding a link to it in the README.

AI Summary: This issue proposes the creation of a new filesystem adapter for storing pastes as JSON files within a specified directory (`DATA_DIR`). The adapter should handle the persistence of pastes, the atomic deletion of expired pastes, and be suitable for simple VPS deployments. It's intended to be a straightforward implementation, serving as a good learning experience.

AI Summary: This issue proposes adding a new documentation file, `docs/deploy-vps.md`, to guide users on deploying the application on a VPS using Nginx or Caddy as a reverse proxy, along with a Node.js process manager. The goal is to provide a vendor-neutral deployment solution.

AI Summary: This issue requests the creation of a new documentation file, `docs/deploy-fly.md`, to guide users on deploying the project to Fly.io. The new documentation should leverage the existing Dockerfile and avoid creating a separate image. The task is considered straightforward, with verification involving checking for the file's existence and a link in the README.

AI Summary: This issue requests the addition of a new documentation file, `docs/deploy-railway.md`, to guide users on deploying CloakBin using Railway. The guide should focus on a static/web service path and reference existing environment variables without introducing new adapters.

AI Summary: This issue proposes adding Portuguese (pt) language support to the project once the internationalization scaffolding is implemented. It involves creating a new locale file, translating all user-facing strings, and integrating it into the locale switcher. The goal is to have a complete translation without relying on English fallbacks.

AI Summary: This issue proposes adding German language support to the project. It involves creating a new locale file, translating all user-facing strings, and integrating the new locale into the existing language switcher. The work is dependent on another issue related to i18n scaffolding.