Find meaningful ways to contribute

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 user locale information (system locale, AnkiDroid language, and backend language) to the "Copy Debug Info" feature. This information is intended to help developers better understand and debug linked issues by providing context about the user's language and regional settings.

This issue addresses a bug where the `_fail` function in the `ship` command incorrectly allows control bytes, specifically the ESC character, to pass through to the terminal after Rich markup has been neutralized. This can lead to unexpected terminal behavior when error messages contain these control characters, especially when they originate from user-provided chat templates. The fix involves ensuring that all control bytes are stripped from messages before they are displayed to the user, maintaining terminal hygiene.

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 marked as a 'good first issue' and eligible for Hacktoberfest.

Flutter FFI plugins are incorrectly classifying vendored Dart SDK C headers as first-party code. This leads to dead code analysis reporting unused exports from these headers. The issue proposes adding 'dart-sdk' to the list of recognized vendored directory tokens to rectify this classification.

The PKCE enforcer is not being applied when configured within a client-id-uri policy for CIMD clients. This allows authorization codes to be issued without PKCE, and the client is not auto-configured with PKCE S256 as expected. The issue stems from the event scope of the ClientIdUriSchemeCondition, which prevents the PKCE enforcer from executing on relevant events.

This issue aims to make Kolibri's queue logging restartable within a single process, addressing a limitation where it can only be set up once. This will involve modifying the core logging mechanism to allow reinitialization and removing a specific workaround currently used by the Android platform.

This issue proposes to refactor the user interface by moving the 'Audio Beacon settings' menu to a more prominent and logical location. Currently nested within 'General Settings', the suggestion is to create a standalone menu for it, positioned between 'Media Controls' and 'Manage Call outs'. This change aims to improve user experience and accessibility for audio beacon configurations.

The `unsloth` backend is currently accepted but silently ignored when used with the `distill` task, causing training to proceed with standard Transformers instead of Unsloth. The issue proposes either refusing this combination at configuration load with a clear message or implementing proper support for Unsloth distillation.

The `gradient_checkpointing` setting in TRL trainers is inconsistently applied, being overridden by internal defaults and quantization logic rather than the user-specified configuration. This leads to `false` not reliably disabling it during 4-bit training and some trainers ignoring the `true` setting.

The `preference_loss_weights` feature in Soup is not functioning as intended because the wrapper expects log-probabilities to be present in the batch, but the `trl` trainer (version 0.29) does not provide them. This causes secondary loss terms to be ignored, and only the primary loss is trained, scaled by its weight.

The front-end is not correctly applying visibility configurations for metadata fields defined in the backend's `submission-forms.xml`. While frontend code has been updated to handle these configurations, the backend's data format for submission forms appears to be outdated, preventing the visibility settings from being enforced.

This issue proposes adding two new JavaScript functions, `invert` and `threshold`, to the npm package. These functions are already available in the WASM module and other language APIs but are currently missing from the JavaScript wrapper. The task involves creating new wrappers that mirror existing patterns, adding JSDoc documentation, and ensuring type safety through tests.