Find meaningful ways to contribute

This issue requests the addition of four missing LLM-related environment variables (`LLM_BASE_URL`, `LLM_API_KEY`, `LLM_MODEL`, `LLM_PROXY`) to the `.env.example` file. These variables are crucial for users wanting to configure their own LLM providers but are currently undiscoverable for those who only use the example file for setup.

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 `sanitizeHtml()` function is incorrectly marked as `async` when its underlying operation is synchronous. This issue proposes removing the `async` keyword and the unnecessary `await` calls at its usage sites to improve performance. The change is expected to have no functional impact.

The user is asking for a way to programmatically check the version of the PDF.js library being used within a document. This likely involves accessing a property or method exposed by the PDF.js library itself to retrieve its version information.

This issue proposes adding a new `size-histogram` verb to the bulk executor. This verb would calculate and display the distribution of item sizes within a table, allowing users to understand how many items fall into specific size ranges. It would also support a `where` clause for filtering the analysis to specific subsets of data.

This issue proposes adding organization-scoped variables and secrets that can be referenced within workflow configurations. Currently, workflows can only reference node-scoped values, leading to duplication of configuration data. The solution requires implementing storage, encryption for secrets, server-side resolution, and UI elements for managing these new organization-scoped entries.

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.

The `scripts/check_subsystem_map.py` script is flagging an unresolvable commit stamp for the 'routing-providers' entry in the documentation. This is because the original commit the stamp pointed to was part of a squash-merged pull request and no longer exists on the default branch. The fix involves re-verifying the 'routing-providers' entry against current code and then re-stamping it with a commit that is an ancestor of the default branch.

This issue requests adding return type annotations to 35 methods in the CLI's HTTP adapter (`palinode/cli/_api.py`). The annotations are based on the return types of the corresponding API endpoints, which are provided in a table. An import for `Any` from `typing` is also required.

The `_read_limited` function in the executor clips subprocess output streams at a defined limit without indicating that data was discarded. This leads to inaccurate reporting of the total stream length, making it appear complete when it has been truncated. The suggested solution is to return a boolean flag indicating truncation and to report the output honestly as a lower bound.

This bug report describes a scenario where COSI can become stuck during the deletion of a Bucket and its associated BucketClaim. This occurs if the Bucket is deleted before the BucketClaim deletion process has fully reconciled, leading to a deadlock where neither resource can complete its deletion due to missing or conflicting annotations.

This issue proposes to improve error reporting for failed video renders in PortOS by retaining and displaying detailed diagnostic information from the H3 engine's exit. The goal is to provide users with more specific reasons for failures beyond a generic exit code, similar to a recent improvement in the Phosphene project.

This issue addresses a security vulnerability in the user creation endpoint where arbitrary request bodies are accepted. The goal is to implement robust validation for incoming user data, ensuring server-side ID generation, email validation, normalization of optional fields, and rejection of malformed JSON payloads. This will enhance the security and integrity of user data.

This feature request aims to integrate ZCode (Z.ai's AI coding agent using GLM-5.2) as a first-class supported agent within the Orca application. Currently, ZCode is not listed in Orca's agent registry, preventing users from selecting it. The proposed solution involves adding ZCode to Orca's supported agent list, potentially by creating a hook script or a wrapper recipe.

When a user switches the distance unit to kilometers for excluding commutes, the setting incorrectly continues to display miles. The unit only updates to kilometers after the user re-saves the commute exclusion distance.

The user is encountering a `json.decoder.JSONDecodeError` when trying to send a JSON request to their application. They are using `requests.post` with the `data` parameter, which by default sends URL-encoded data, not JSON. The application code expects JSON, leading to the decoding error.

The link for the "Introduction to Reinforcement Learning" on the homepage README is incorrectly configured. It currently points to 'intro.md' but should be 'introduction.md'. This is a straightforward text correction.

The user is encountering discrepancies in the Value Iteration algorithm's output, specifically regarding the initialization of terminal state values. They question the current implementation where terminal states are assigned their reward value, and this value is also used in the Bellman backup for transitions into terminal states. The user proposes that terminal states should typically have a value of 0, with rewards only affecting the transition cost.

This issue reports a critical content error where the English version of a book is incorrectly displaying Chinese text. This suggests a potential issue with content management, file handling, or localization processes within the project.

The user is asking if the project would consider adding a section related to OPD (likely referring to Object-Oriented Programming Design or a similar concept). They are offering to provide articles and are seeking guidance on how to contribute them and where they would best fit within the existing structure.

This issue proposes collecting and showcasing high-quality community videos demonstrating the practical application of "Agent Skills." The goal is to highlight these skills through various formats, including individual skill demonstrations, full project walkthroughs, setup guides across different tools, and before/after comparisons.

This issue proposes improvements to the "floating titles" feature in the entry table, which displays full titles when they are truncated. The user finds these floating titles intrusive, especially with their custom theme, and suggests making them conditional (only appearing when needed), adding a toggle, or increasing their delay.

Client policies using `ClientUpdaterSourceGroupsCondition` and `ClientUpdaterSourceRolesCondition` are causing `ClientPolicyException` errors when CIMD clients trigger registration or update events. This is due to an 'unexpected context type' error in the condition evaluation, preventing these client policies from functioning correctly for CIMD clients.

This issue proposes an enhancement to the @docsearch/react component to allow users to select multiple values within facet dropdowns. Currently, only a single selection is permitted, which is problematic for use cases like Docusaurus where multiple tags can be applied. The solution involves modifying the dropdown to support multi-selection and adjusting the search request to handle an array of facet values.

This issue is a beginner-friendly task to add a new fun fact about Japan to a JSON file. No coding is required, and the contribution can be made directly in the browser within a minute. It's an excellent opportunity for first-time open-source contributors and is tagged for Hacktoberfest.

This issue aims to improve test coverage for the `ActionItem.ts` GraphQL type resolver. The tasks involve reviewing the Codecov report to identify uncovered code, creating a new test file, and implementing test cases for authentication, authorization, empty/null scenarios, and successful data retrieval, following a black-box testing approach with mocked GraphQL context.

The daily scheduled run of the stale.yml workflow lacks failure alerts. If this workflow fails, there's no notification, leading to unmanaged stale issues and PRs. This is a recurring issue across several other scheduled workflows in the repository.

This issue requires verifying that the `observe()` function can correctly identify and instrument a Groq client instance using duck-typing. The task involves checking the provider detection logic, adding a unit test with a mocked Groq client, and potentially updating the duck-typing rules if detection fails. The goal is to ensure Groq is recognized as a distinct provider and not misidentified as OpenAI.