Svelte good first issues

This issue outlines a roadmap for future development, focusing on key features like remote instrumentation, concolic execution, improved workspace summarization, and enhanced disassembly capabilities. Several items are marked as important and require immediate attention, including remapping support for disassembly and propagating method mappings across subclasses.

This issue discusses the integration of Playwright tests into the AdventureLog project for both local and CI environments. While local tests are working, the author is encountering issues with tests failing in GitHub Actions, specifically with the adventure popup rendering incorrectly, which prevents tests from progressing.

This issue proposes to improve the icon used for 'Compare mode' to make it more intuitive and easily recognizable for users. The process involves evaluating and selecting a new icon, implementing it in the UI, and ensuring it meets accessibility standards.

This issue proposes adding line numbers to the raw markdown view, similar to how they are displayed in the editor. The goal is to improve usability by allowing users to easily reference specific lines in the raw content, as this is a common requirement for reading and collaboration. The ideal solution would reuse the existing gutter implementation from the editor to ensure consistent alignment and appearance.

This issue proposes adding support for reading paste content directly from standard input (stdin) in the CLI. This will allow users to pipe data into the `cloakbin create` command, making it more integrated with existing Unix workflows and shell pipelines. The implementation should handle explicit '-' arguments and also default to stdin when data is piped in.

This issue proposes a comprehensive audit of security-related HTTP headers across different application contexts (HTML, API, static). The goal is to ensure these headers are configured according to a defined baseline, with any discrepancies documented, fixed, or explicitly waived. The implementation should involve updating middleware and potentially documentation.

This feature request proposes adding a global memory quota to DiscoPanel to prevent users from overcommitting host resources. Administrators would set a total memory limit for all Minecraft servers, and the system would prevent new servers or memory increases that exceed this global cap. This aims to provide a safety net for multi-user environments, allowing users to manage servers without risking host instability.

This feature request proposes adding a new API endpoint that allows users to download a modpack zip file by providing its slug. This functionality is intended to facilitate the distribution of modpacks to clients.

The user suggests implementing a feature to allow partial configuration syncing within files. This would enable users to customize specific settings while still receiving updates from modpacks for other parts of the configuration, preventing outdated settings after auto-updates.

A user is reporting a severe and reproducible memory leak within Discopanel running in a Proxmox LXC container. The Discopanel process rapidly consumes gigabytes of RAM, causing the entire LXC to become unresponsive, despite the LXC having a large RAM allocation. The issue appears to be isolated to Discopanel itself, as the Minecraft servers it manages do not show a corresponding increase in memory usage.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.