Help Wanted

AI Summary: This issue proposes investigating the `fearless_simd` crate as a potential dependency for performance improvements through SIMD vectorization. The task involves a code review of the crate's quality and maintainability, a prototype implementation on a critical component (polynomial.rs), and consideration of build system implications.

AI Summary: This issue highlights a discrepancy between a secret's `retention_time` and its actual deletion time due to the default `cleanup_schedule`. The default cleanup runs every 10 minutes, meaning a secret set to expire in 5 minutes might not be deleted until the next cleanup cycle, leading to a potential delay of up to 10 minutes. The author suggests decreasing the default `cleanup_schedule` to reduce this inaccuracy.

AI Summary: This issue is a beginner-friendly task to add a new anime quote to a JSON file. It requires no coding and can be completed directly in the browser by forking the repository, editing the `anime-quotes.json` file, and submitting a pull request. The quote is for "JoJo's Bizarre Adventure: Stardust Crusaders" by DIO.

AI Summary: This issue is a beginner-friendly task to add a new Japanese grammar point, "〜やすい", to a JSON file. It requires no coding and can be completed in under a minute by forking the repository, editing the JSON file directly in the browser, and submitting a pull request.

AI Summary: This issue proposes benchmarking different vector quantization techniques (binary, int8, float16) against the current float32 baseline to reduce storage and improve cache performance. The goal is to find a representation that offers significant memory or latency gains without unacceptable retrieval quality degradation, using realistic datasets and reporting key performance metrics.

AI Summary: Users are unable to install personal or CI-built Android apps alongside the official store-signed app because they share the same application ID. The proposed solution is to allow build invocations to opt into a distinct package ID using a Gradle property, enabling side-by-side installation and clear differentiation through launcher labels.

AI Summary: This issue addresses incorrect guidance in the admin interface's empty state. The current message suggests that lights appear after Stoplight blocks are run, which is outdated for v6. The proposed change updates the message to reflect that lights are registered at registration time and require a shared Redis-backed system.

AI Summary: This issue proposes improving the admin interface to provide clearer information about when an unlocked red light can begin recovery. Currently, users only see a generic message, making it difficult to gauge the time remaining or if recovery is even possible. The change involves displaying a relative deadline or eligibility status for unlocked red lights, while ensuring locked red lights do not imply automatic recovery.

AI Summary: This issue addresses inaccurate messaging on "yellow cards" in the admin interface, which currently misrepresents the recovery mechanism as a fixed one-request budget. The proposed solution is to update the messaging to accurately reflect that recovery probes run one at a time and, ideally, to display the actual progress of recovery probes against the defined threshold.

AI Summary: The current admin interface incorrectly displays the last error time as the 'Last Check' even when successful requests have occurred more recently. This issue proposes to update the logic to show the most recent activity, whether it was a success or a failure, and to label it as 'Last Activity' to accurately reflect the light's operational status.

AI Summary: This issue addresses a misleading display of failure metrics in the admin dashboard. Currently, 'Failures' is shown as a consecutive error streak, which can be zero even when errors are present in an active window. The proposed change is to accurately represent the metrics based on their actual semantics, distinguishing between consecutive failures and windowed error rates.

AI Summary: The terminal composer currently provides no visual distinction between slash commands and regular messages, making it difficult for users to differentiate them before pressing Enter. This feature proposes to visually highlight the command token in the terminal composer, similar to the web composer, to improve clarity and prevent confusion, especially with skill commands.

AI Summary: This issue proposes to add the OpenSSF Mentorship Program to the project. It's labeled as a 'good first issue', suggesting it's a straightforward task suitable for new contributors. The goal is likely to integrate information or a link related to this program.

AI Summary: The OpenTelemetry C++ SDK's configuration parser supports general attribute limits, but the SdkBuilder currently ignores them. This issue requires updating the SdkBuilder to pass these general limits to the Tracer and Logger providers, ensuring they are applied when provider-specific limits are not set, as per the specification. Unit tests will be added to verify this behavior.

AI Summary: This issue highlights that pull requests modifying only files within the 'web/' directory currently bypass all CI checks, including basic syntax validation. The proposed solution is to introduce a minimal CI workflow that specifically targets 'web/**' files, starting with a Node.js syntax check for JavaScript files, to prevent accidental merges of broken code.

AI Summary: This issue is a beginner-friendly task to add a new trivia question about animals associated with Inari shrines in Japan to a JSON file. No coding is required, and the contribution can be made directly from the browser in under a minute.

AI Summary: This issue is a "Good First Issue" that invites contributors to add a new Japanese haiku to a JSON file. The task requires no coding and can be completed in under a minute directly from the browser by forking the repository, editing the specified JSON file, and submitting a pull request.

AI Summary: The `rtk rewrite` command incorrectly transforms multi-file `cat` commands into `rtk read` commands that only accept a single file. This causes all multi-file `cat` operations to fail with an "No such file or directory" error, impacting agent sessions that rely on this functionality. The suggested fixes are to either allow `rtk read` to handle multiple files or prevent `rtk rewrite` from modifying `cat` with multiple arguments.

AI Summary: A stale `~/.grok/version.json` file can cause the Grok CLI to use an outdated version, leading to compatibility issues and HTTP 426 errors. The current version resolution logic prioritizes this local file over a default minimum version, effectively bypassing the intended compatibility floor.

AI Summary: This issue addresses a testability gap in the xai-oauth module. While production behavior is correct, the `GrokCliHeaderDeps` are not being fully forwarded through the endpoint layer, preventing deterministic testing of the Grok CLI version resolution chain. The proposed solution involves forwarding these dependencies and adding endpoint-layer tests to cover environment overrides and file fallbacks.

AI Summary: The user is exploring the feasibility of using the `nektos/act` GitHub CLI extension to emulate GitHub Runners within their test suite. This would allow for self-testing of workflows without needing to deploy to actual GitHub Runners.

AI Summary: The harness bench incorrectly expects a binary named 'antigravity' when the actual binary installed and used by omnigent is 'agy'. This causes the harness to report that 'antigravity' is not installed, even when it is present. The suggested fix is to update the mapping in `tests/harness_bench/manifest.py` to correctly associate 'antigravity-native' with the 'agy' binary.

AI Summary: The `ModelOverrideProbe` incorrectly reports `SUPPORTED` for native TUI harnesses, even when no model override is actually applied or sent. This leads to inaccurate capability reporting, as the system claims support for a feature it never exercised. The probe's logic needs to be adjusted to reflect whether a model override was truly used, or to report `SKIPPED`/`UNKNOWN` when none is.

AI Summary: This issue is a beginner-friendly task to add a new Japanese proverb to a JSON file. No coding is required, and the contribution can be made directly from the browser in under a minute. It's an excellent opportunity for new contributors to make their first open-source pull request.

AI Summary: Copr builds are failing for Fedora 45 and rawhide chroots since version 3.15.0 due to issues building `cbor2` and `grpcio` from source in Python 3.15 environments. While supported chroots build successfully, the overall Copr state incorrectly shows as failed, making the build status unreadable and potentially impacting future releases.

AI Summary: The `scripts/validate-places.mjs` script has several blind spots, failing to validate data integrity for place types matching filenames, ID patterns, `valid_till` date formats, and near-duplicate coordinates. It also doesn't handle variations in the `added_by` field. The fix involves correcting specific data errors and extending the validator to enforce these rules and warn about potential issues.

AI Summary: This issue identifies that unit tests are not being run in the CI pipeline, potentially leading to silent test rot. It also points out the lack of scheduled jobs for data freshness checks and proposes adding unit tests to the CI, implementing a scheduled workflow for data validation and freshness, and a follow-up for end-to-end testing.

AI Summary: This issue requires updating the Helm cheat sheet documentation to reflect a flag change in Helm 4. The `--force` flag for `helm upgrade` has been renamed to `--force-replace`, and this change needs to be applied to the cheat sheet, including adding it to the install section for consistency. The existing "in-progress" banner for Helm 4 should remain.

AI Summary: The iOS companion application is crashing due to a kernel-level `EXC_GUARD` when a terminal surface is torn down, specifically when `close(0)` is called on file descriptor 0. This occurs during session switching, which involves removing a terminal view from the window, leading to the process being killed without an opportunity to recover.

AI Summary: This issue addresses several minor but important housekeeping tasks in the project's `package.json`. It aims to add missing scripts for formatting and type checking, move the `shadcn` CLI from production to development dependencies, and ensure version consistency between `eslint-config-next` and `next`. These changes will improve developer experience and maintainability.