Find meaningful ways to contribute

This issue is a meta-task to track the addition of missing Storybook story files for various pages within the project. It serves as a checklist for developers to ensure comprehensive component documentation and testing coverage.

This issue proposes adding a keyboard shortcut to open Kitty's chat interface, improving user workflow. The implementation involves modifying the extension's manifest to define the command, updating the UI to display the shortcut hint, and documenting it in the README. The suggested shortcut is Alt+K (or MacCtrl+K on macOS).

When resizing the browser window after opening a context popup in the Wallet settings, the popup does not reposition correctly. This issue has been reproduced on Windows and MacOS Chrome and Safari browsers.

This issue requests the removal of the API documentation button from the left sidebar of the client application. The button is considered clutter and the API documentation is accessible directly via URL. The task involves modifying the `LeftSidebar.tsx` file to delete the button element and its associated import, and updating a test file to remove a redundant test. The server-side API documentation will remain accessible.

This issue requests a UI enhancement to consistently display a filter count badge next to the 'Filters' header on the Alerts page. Currently, the badge only appears when filters are active. The goal is to always show the badge, including a '0' count when no filters are selected, to prevent layout shifts and improve user experience.

This issue requests the addition of unit tests for the admin user management API endpoints. The goal is to ensure that these endpoints function correctly when accessed by an administrator, covering various scenarios like invalid inputs, existing data conflicts, and password reset functionality. A new test file will be created to house these tests.

This issue addresses inaccuracies in the `adding-alerts.md` documentation. It requires correcting the explanation of the alert integration model from pull to push via webhooks and updating the alert states from 'Active'/'Dismissed' to 'firing'/'resolved', including the 'silenced' and 'unread' flags.

This issue proposes renaming the "Overview" sidebar pill to "Source Pressure (SP)" to better reflect its content, which represents the total open issues and pull requests from configured sources. The change involves updating the pill's display to "SP = X/Y" and modifying its tooltip to include the new term, while ensuring it fits within the sidebar at phone widths. A glossary definition will also be added.

This issue requests the completion of the Spanish translation for the `c-api/cell.po` file, aiming to reach 100% translated. Currently, 90.9% of the file is translated, with only one untranslated entry remaining. Interested contributors are encouraged to comment to be assigned the task.

This issue proposes to incrementally type-annotate six legacy core modules within the skillware framework. The goal is to remove existing mypy overrides and enforce strict type checking across the entire skillware package, improving runtime reliability and developer experience.

This issue proposes adding an option to Fourmolu to allow indentation with tabs instead of spaces. The user highlights accessibility benefits and the potential for editor configuration as reasons for this feature, citing a similar discussion in Prettier. The proposed solution involves a configuration setting like `indent-style: tab`.

A user is experiencing reboots on their Xiaomi 2409FPCC4G device running Android 14 after attempting to trigger a hook with DFRoot versions 3.3 and 4.1. The device crashes with SIGSEGV errors in critical system processes like 'init' and 'netd' after the hook is triggered, preventing root access. The user suspects issues with executable memory mapping or SELinux compatibility.

A bug in the Metal parser causes legal function names like 'read' to be misinterpreted as declarations, leading to translation failures for Metal, OpenGL, and DirectX backends. This issue needs to be fixed to correctly parse contextual Metal access names as function identifiers, ensuring proper handling of global, namespace-qualified, and overloaded functions.

This issue proposes the creation of a validating webhook for the Burrito project. The webhook will be responsible for validating resources before they are applied, specifically focusing on the `remediationStrategy` enum and complex interactions between various options.

This issue requests the implementation of a new Git provider for Bitbucket. It specifically mentions building upon the new structural changes introduced in a recent pull request, indicating a need to integrate with an existing framework.

This issue proposes adding a new configuration setting to the Burrito tool. This setting would prevent Burrito from executing 'apply' operations if the 'plan' output indicates that any resources are scheduled for destruction. The goal is to enhance safety and facilitate adoption on critical Terraform code by preventing accidental resource deletion.

The user wants BliKVM to support the Dvorak keyboard layout. Currently, BliKVM sends QWERTY keycodes regardless of the host's OS input settings, causing input mismatches for Dvorak users. The desired functionality is for BliKVM to respect the OS keymap or allow remapping of keycodes.

This feature request proposes importing database connection credentials directly from project configuration files like .env and Docker Compose. The goal is to streamline the process of connecting to a project's database by automatically detecting and suggesting credentials, avoiding manual retyping. The implementation will involve scanning project folders, parsing configuration files, and presenting discovered candidates for user review and import.

The `soup draft distill --plan-only` command previews YAML output, but long paths within quoted values are incorrectly wrapped at the console width. This wrapping can alter the path when copied, leading to potential errors. The suggested fix involves enabling soft wrapping and adding a test case for narrow console widths to ensure the YAML remains intact.

This issue requests a frontend-only enhancement to display the bound authority reference in citation ledger rows. Currently, these references are not visible, leading to generic labels. The change involves modifying a Svelte component to show the `external_ref` field from the `LedgerSource` type, along with adding relevant tests.

This issue proposes adding support for OSv, a popular unikernel framework, to `urunc`, a unikernel container runtime. This enhancement would expand `urunc`'s compatibility and provide more examples for users.

This issue describes a user experience problem where a run that successfully produced an artifact is incorrectly reported as failed. The failure notification obscures the fact that a usable artifact was generated, leading to user confusion and a lack of visibility into the successful output. The requested fix is to display the artifact alongside the failure message or to reclassify the scenario as a warning, and to ensure artifacts are visible even when prose output is missing.

This issue requests the addition of new tests to ensure complete branch coverage for the Python backend code. Contributors are asked to identify and fix missing branch coverage in specific files, aiming for a 100% branch coverage report. Additionally, scripts for checking overall backend test coverage will be updated to enforce this new branch coverage requirement.

This issue proposes renaming fields within the `Credential` struct in the `credentialsd_common::model` module. The current field names `name` and `username` are confusing as they are swapped in their intended meaning. The goal is to align these names with their actual purpose or with the WebAuthn specification for clarity.

In Keycloak 26.7.4, the `ResetCredentialsActionToken` constructor and its expiration parsing logic still use `int` for expiration timestamps, despite the migration to `Time.currentTimeSeconds()` which returns `long` to prevent the year 2038 problem. This causes compilation errors when trying to pass `long` timestamps and reintroduces the overflow risk when casting back to `int`.

This issue proposes to refactor error checking in sqllogictest files by converting escaped regex error messages into plain text. The goal is to improve readability and maintainability of test files by replacing complex regex patterns with straightforward expected error outputs.

This issue proposes consolidating the `SearchEngine` class across Android and Desktop platforms by introducing adapter parameters. This aims to resolve implementation discrepancies, particularly in how search engine settings are managed and how the Telluride video search tool is interacted with on each platform.

This RFC proposes an LLM-ranked knowledge advisor for agents, building upon a previous phase that offered basic, unranked knowledge hints. The advisor would leverage a small LLM to rank candidate knowledge entries based on the agent's current task and recent activity, aiming to improve relevance and timing of suggestions. Key discussions include whether the LLM should rank existing knowledge or generate new hints, and how to manage the computational budget.

This issue proposes a significant architectural change to move Crux development entirely to the `hivecommons/crux` repository, making it the definitive source of truth. The existing publish/sync pipeline will be retired, and the main `hive` repository will consume `hivecommons/crux` as a standard Go dependency. This transition is planned for November 16, 2026, with preparatory work occurring in the preceding week.

This issue serves as a central hub for advisory findings from Hive agents, particularly at lower ACMM levels where agents analyze code without creating direct issues or PRs. A governor agent periodically posts digest comments summarizing these advisory findings. This issue is intended to be a living document and should not be closed.