Find meaningful ways to contribute

This issue proposes the removal of an unused `DocPageActions` component and its associated `html2pdf.js` dependency. The component is not imported anywhere in the project, and its removal will clean up the codebase by eliminating an unused production dependency and its type definition file.

This issue requests the removal of several unused component files from the `src/components/` directory. These components are identified as leftovers that are never imported or used within the codebase, including tests and MDX files. The goal is to clean up the codebase by deleting these files after confirming their non-usage.

This issue identifies a potential race condition in NFSv3 dentry caching that could cause the `readAuditLease` to remain stale for longer than its 45-second TTL. This could lead to a situation where a non-holder pod might incorrectly take over a lease that was just renewed, potentially causing both pods to write to the audit log concurrently for a short period.

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.

This issue proposes adding a fallback screen for the mobile scanner when camera permissions are denied. This screen will provide instructions to the user and a button to directly open system settings for granting the permission.

This issue proposes adding a currency preference selector to the mobile app's settings. Users will be able to choose between USD, EUR, XLM, and NGN, with prices dynamically converting based on real-time exchange rates. The selected preference will be stored locally using AsyncStorage.

This issue asks to add unit tests for the `Neo.core.IdGenerator` class, which is responsible for generating unique IDs for Neo instances. The tests should verify that IDs are generated with the correct prefix and that counters are maintained independently for different names, as well as a shared counter for default or empty names. The goal is to ensure the `IdGenerator` functions as expected and to establish a baseline for testing this core engine component.

Two GitHub issues were incorrectly labeled as 'stage/030-pr-in-progress' and 'hive/claimed-by-scanner' due to a bug in how agent comments and label requests were interpreted. The system treated report-only comments and verification labels as signals that the agent had started work, leading to false claims. The root cause lies in the `issueRequestStartSignal` function and the `IssueClaimBlockReason` logic, which were too permissive.

This issue addresses a critical logging gap in the server where various types of errors, including those from custom knowledge sources, lead capture callbacks, and webhooks, are silently swallowed. The goal is to implement `console.error` logging for these specific failures to provide visibility to operators without altering the user-facing error message or exposing sensitive data.

This issue proposes the deletion of an unused copy of `yamlValidation.ts` located in `ui/src/utils`. This file is a duplicate of the one in the design-system package and is not imported by any part of the UI or related packages. The task involves confirming its un-usability through specific grep commands before proceeding with its removal.

This issue introduces a central stage engine for managing GitHub issue and PR labels. It aims to simplify label management by deriving labels from GitHub's state, using a state machine approach, and implementing a phased rollout with shadow and enforce modes. The plan involves several parallel and sequential Pull Requests to build out the new engine and integrate it into the existing system.

This issue requests the addition of a new runnable example for the `@cogitator-ai/redis` package. The example should demonstrate direct usage of the Redis client, including configuration, key manipulation with prefixes and TTLs, atomic operations like `incr`, and pub/sub functionality, all against a local Redis instance. The goal is to showcase features not currently covered by existing examples.

This issue proposes adding a new WebAssembly (WASM) tool called `textcase` to the `@cogitator-ai/wasm-tools` library. This tool will convert text into various code-related casing styles (camel, snake, kebab, etc.) and also return the detected words from the input. The implementation involves creating a new plugin, defining its schema and factory function, and writing comprehensive tests, following the pattern of the existing `slug` tool.

This issue proposes adding a new WebAssembly (WASM) tool to the `@cogitator-ai/wasm-tools` library for deterministic unit conversions. The tool should handle various categories like length, mass, temperature, and data, supporting both standard and binary prefixes. The implementation should be data-driven for easy extensibility and follow a specific structure for WASM plugins.

This issue proposes adding a new WebAssembly (WASM) tool to the `@cogitator-ai/wasm-tools` package. This tool will provide two core functionalities: converting color formats between various representations (hex, RGB, HSL) and calculating WCAG 2.x contrast ratios for accessibility checks. The implementation should follow the existing structure of other WASM tools within the project, including creating a new plugin file, updating the main index file with schema and factory functions, and adding comprehensive tests.

This issue proposes adding a new 'similarity' metric to the `@cogitator-ai/evals` library. This metric will use the Levenshtein distance to provide a score between 0 and 1, indicating how similar two strings are, rather than just a pass/fail. It will include options for case sensitivity and whitespace trimming, and will be integrated with existing assertion mechanisms.

This issue requests the addition of a README file for the `@cogitator-ai/server-shared` npm package. The README should explain the package's purpose, its target audience, detail its exports, provide a usage snippet, and list dependent packages. The goal is to improve the discoverability and understanding of this core shared library.

This issue outlines the comprehensive checklist for the HugeGraph 1.8.0 release, focusing on functionality, compatibility, documentation, and cross-repository integration. It details specific tasks for HugeGraph Server, Toolchain, AI, website, and documentation, including Kubernetes/Helm support, various deployment configurations, and authentication mechanisms.

This issue addresses three security advisories in the project's dependencies: source-map-js (high severity), smol-toml, and uuid. A simple `npm audit fix` command can resolve these vulnerabilities by updating the lockfile. The task involves running this command, committing the updated lockfile, and ensuring tests pass.

The transaction detail page is failing because it references an undefined `network` variable and a non-existent `findTransactionByHash` function. The issue requires restoring or inlining the `findTransactionByHash` function, correctly constructing the `requestKey` with network information, and ensuring tests pass.

A GitHub Actions workflow permission tightening was incorrectly flagged as requiring human intervention, delaying an automated merge. The issue stems from a rule that mandates human approval for permission changes, even when those changes only reduce permissions and pose no risk. This false positive hinders unattended automerge for trusted agents.

The `stellar-wallets-kit` library, specifically version 2.6.0, pulls in vulnerable dependencies like `elliptic`, `stream-json`, and `@solana/web3.js` through its `@hot-wallet/sdk` dependency. This introduces security risks, and the only current fix involves a breaking downgrade to version 1.5.0.

The root layout in Next.js 16 is attempting to synchronously access headers, which are now asynchronous. This causes a TypeScript error. The issue also notes that the retrieved nonce value is unused, and proposes making the root layout async to correctly handle the asynchronous headers and pass the nonce to relevant scripts.

The CI pipeline fails to generate coverage reports because the necessary `@vitest/coverage-v8` dependency is missing and the `vitest.config.ts` file lacks a coverage configuration. This causes the coverage step to fail silently due to `continue-on-error`, preventing any coverage data from being collected or uploaded.

The `fundingSchedules.ts` file is corrupted, with its public API truncated and missing essential imports. This has caused compilation errors in the schedules page and its tests, as well as incorrect network handling and data validation issues. The fix involves restoring missing exports, correcting network imports, and ensuring consistent network type declarations and validation.

The `WidgetPageInner` component incorrectly places `useState` and `useEffect` calls after an early return. This violates React's rules of hooks and can lead to errors if the component's props change, causing it to render fewer hooks than expected. The fix involves moving the hook calls above the conditional return and guarding their execution.

ESLint 9 in this repository uses a flat configuration file (`eslint.config.mjs`) and ignores the legacy `.eslintrc.json` file. This means rules defined in `.eslintrc.json`, such as those for unused variables and console warnings, are not being applied. The task involves migrating these rules and test file overrides to the new configuration and then deleting the old file.

The `/api/simulate` endpoint is attempting to import and use a rate limiting module that does not exist at the specified path or with the expected signature. The existing rate limiting module (`rateLimit.ts`) has a different naming convention and function signature, preventing the simulation endpoint from working correctly and causing UI fallbacks. This issue requires updating the import path and function calls to match the existing rate limiter and potentially creating a new helper function for the response.

This issue addresses a bug where the widget still uses an old source identifier ('aframp-widget') and branding instead of the new one ('caddress-widget'). The fix involves updating hard-coded message sources, renaming the header, and ensuring the correct loader file and documentation are used.

The runs-service is experiencing performance bottlenecks due to sending individual PostgreSQL NOTIFY calls for each action update. This results in a full network round trip for every notification, limiting throughput. The proposed solution is to batch these NOTIFY calls to reduce the number of round trips and improve overall performance.