Find meaningful ways to contribute

This issue proposes adding a dedicated tokenizer for Gemini models to provide exact token counts, similar to how it's handled for Anthropic models. Currently, Gemini users only receive an approximation. The solution involves creating a new `gemini_tokenizer.py` file, integrating it into the existing tokenizer system, and ensuring proper error handling and testing.

This issue reports C linting failures detected in the automated workflow for the stdlib-js project. Specifically, the `iget_ptr.c` file has style warnings indicating that the `strides` and `shape` variables could be declared as pointers to const. The fix involves updating these declarations to adhere to the linting rules.

A hive instance is experiencing a "mutation-ledger" component error where a "branch_update" operation has been stuck in an "Unknown" state for over 35 minutes, refusing retries. This indicates a potential deadlock or failure in the operation's state management within the hive's ledger.

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. The governor will periodically post summaries of these advisory findings. It's crucial not to close this issue as it's intended to be a continuously updated document.

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.

This issue requires building a mechanism to read stored content by its address from an object store. This is crucial for M2 grounding and involves creating a read path that connects to the existing object store, ensuring data can be retrieved accurately and efficiently.

This issue serves as a curated list of open tasks for potential contributors to the Octomind project, categorized by estimated difficulty (easy, medium, hard). It outlines the process for claiming an issue, provides links to relevant documentation, and encourages questions. The list includes bugs, feature requests, documentation updates, and test improvements.

Ten Rust source files are missing or have incorrect Apache 2.0 license headers as specified in AGENTS.md. This issue requires fixing the existing headers in these ten files and implementing a new test to automatically verify license headers in all `.rs` files to prevent future occurrences.

The `octomind config` command incorrectly handles combinations of flags. Specifically, flags like `--show`, `--validate`, `--list-themes`, and `--upgrade` exit early, causing any subsequent configuration change flags (e.g., `--model`, `--api-key`) to be silently ignored. The proposed fix involves using `conflicts_with_all` in the argument parsing library to prevent these invalid combinations and provide clear error messages.

This issue requires designing a lawful normalization mechanism for a transformer model that currently lacks one. The mechanism must operate solely on geometric principles, avoiding operations like softmax or matrix multiplication, and adhere to specific charter requirements. The design should be documented with a proposal and a pre-registered test demonstrating its effect.

This issue is a beginner-friendly task for Hacktoberfest, asking contributors to add a classic Japanese haiku to a JSON file. No coding is required, and the contribution can be made directly from the browser in under a minute.

This issue reports that Kustomize v4.4.1 generates ConfigMap items in a random order, leading to inconsistent YAML output. While functionally equivalent, the user desires reproducible and consistently ordered build outputs for better predictability.

This issue describes a bug where the "first sweep window" in the review backlog system fails to recover hosts that were closed before a deployment. This means issues closed prior to the deployment are not correctly processed unless they are updated again. The fix is blocked by a specific pull request (#13936) which needs to be merged first.

When a user attempts to trash a file they lack write permissions for, the trash-rs crate creates an orphaned placeholder file in the trash directory without a corresponding `.trashinfo` file. This violates the FreeDesktop trash specification and can lead to a corrupted trash state. The issue suggests either pre-checking permissions or implementing cleanup logic to remove incomplete trash entries.

The `reticle serve --http --http-port <bridge port>` command fails with an `EADDRINUSE` error because it attempts to use the same port for both the HTTP verify endpoint and the existing bridge port. The error message is not informative, failing to mention that the bridge port is already in use and that `--http` starts a verify endpoint.

The `summary.layoutShift` metric is incorrectly accumulating layout shifts caused by Reticle's own HUD, leading to inflated values. The issue requires filtering out shifts originating solely from the HUD and ensuring the metric reflects shifts only within the action window.

Text content appended directly to the `<html>` element (outside of the `<body>`) is not being detected by `find` or `text` checks in the browser adapter. The issue requires either an informative error message when such text is not found, or an update to the default container to include these elements.

The `reticle_act` function incorrectly handles non-string values for the `name` field within the `target` object. Instead of rejecting invalid input, it drops the `name` field, leading to unintended matches and actions. The expected behavior is to refuse the operation with an error message specifying the invalid field.

The current tool description for `reticle_act { steps }` does not explicitly mention that the verdict for each step is stored in the `steps[].held` field. This leads agents to incorrectly infer success when `tail` is null. The fix involves updating the tool's description to include `steps[].held`, `steps[].observed`, and `steps[].stopped_at`.

The documentation for the `claim` parameter in `reticle_session` is insufficient, as it doesn't specify the allowed values (`pass`, `fail`, `partial`). This leads to agents incorrectly using the parameter, causing calls to be refused. The fix involves updating the tool description to list the valid enum values.

The `yield` action in the `reticle_session` tool incorrectly assigns a waiting state to a different active tab when the specified `sessionId` has already been closed. This behavior deviates from the `end` action, which correctly refuses to substitute sessions. The fix involves ensuring `yield` also checks for departed sessions and returns an appropriate message without altering other active sessions.

The Reticle tool fails to observe network requests originating from same-origin iframes because its network patching is only applied to the top-level window. This results in a 'blind spot' where requests from iframes are missed, causing checks like 'settled' to incorrectly report completion. The goal is to extend network instrumentation to all same-origin iframes, both existing and newly loaded.

This issue describes a problem where certain features that rely on a context menu (right-click) cannot be triggered by the current automation tools. The existing actions for clicking or simulating keyboard shortcuts do not fire the necessary `contextmenu` event, preventing the feature from being tested or used. The goal is to implement a new action that correctly simulates a right-click and triggers the context menu.

This issue describes a problem where the `scroll` action directly manipulates scroll positions instead of simulating a `wheel` event. This prevents smooth-scrolling libraries, which rely on `wheel` events, from functioning correctly and verifying their behavior. The proposed solution is to add an option to dispatch `WheelEvent`s, allowing pages to handle scrolling naturally.

The `reticle verify` command fails to perform signed-in checks when the MCP daemon is running and occupying the bridge port. The issue arises because the CLI cannot acquire a new tab from the daemon to perform the check with a provided storage state, leading to errors indicating port busy or incompatible options.

The `serve --drive`, `drive`, and `verify` commands in the Reticle CLI fail when connecting to a development server using a self-signed certificate. This is because the CLI lacks an equivalent option to `reticle_lease`'s `ignoreHTTPSErrors` setting, preventing agents without MCP tools from accessing such servers. The proposed solution is to add a `--ignore-https-errors` flag to these CLI commands.

The issue describes a bug where a 'find' action with a scope that matches nothing incorrectly returns a count of 0, leading users to believe an element is absent when the scope itself was not found. This also affects 'element' predicates with 'absent: true', which can pass even with a mistyped scope. The desired behavior is for missing scopes to either be omitted from the count or result in an error, and for absence checks over missing scopes to be graded appropriately.

The `reticle doctor` tool incorrectly reports a daemon's link as healthy even when the daemon has stopped responding to requests. This is because it relies on stored records instead of actively checking the daemon's responsiveness. The issue proposes that `reticle doctor` should send a timed MCP request to verify the daemon's status and provide appropriate feedback, including recommending `reticle restart --force` when necessary.