Help Wanted

AI Summary: Users are reporting that custom MatTooltips in the Fineract Backoffice UI are not disappearing as expected after interaction. This leads to tooltips remaining visible even when the user moves focus or interacts with other elements, potentially causing multiple tooltips to overlap.

AI Summary: This issue proposes adding a "Save changed positions" rewrite rule to the fault-equivalent (FE) mode within the OCM (On-Chip Memory) system. The goal is to make this useful rule available in the FE mode for enhanced functionality.

AI Summary: This issue describes a bug where the agent incorrectly flags contradictions in assertions due to stale events from previous, unrelated actions or ended sessions remaining in the event buffer. This leads to false negatives (verified: no) and undermines the reliability of the agent's contradiction detection, potentially causing users to ignore valid warnings.

AI Summary: The agent's 'idle settlement' mechanism incorrectly overrides explicitly defined 'until' predicates, causing verifications to fail even when the expected conditions are met. This leads to provable passes being reported as 'unknown' or 'unsettled', hindering the ability to reliably verify application states and changes.

AI Summary: The `act_sequence` function times out during long batches of actions without reporting per-step progress, making recovery difficult and expensive. The issue proposes adding per-step progress reporting, making timeouts configurable, and distinguishing between unanswered commands and budget exhaustion to improve recoverability and user experience.

AI Summary: The MCP daemon incorrectly assumes the project's `.reticle.json` configuration file is in its current working directory. This causes issues in monorepo setups where the daemon might be launched from a different directory than the project's root, leading to agents failing to detect wired projects. The suggested solution involves a more robust search for the configuration file, including upward traversal to the repository root and scanning common workspace directories.

AI Summary: The current error message for a disconnected session in the agent incorrectly prioritizes a port mismatch as the primary cause, which is rarely the actual issue. It also suggests running `init` on already configured applications, leading to wasted developer time and misdirection. The fix involves re-ranking potential causes based on information the daemon already possesses.

AI Summary: When the browser SDK refuses to connect, the error is only visible in the page's console, which is inaccessible without a session. This creates a loop where the agent cannot diagnose the refusal. The documentation also incorrectly states that `allowNonLocalhost: true` is sufficient for non-localhost connections, when a pairing token is also required.

AI Summary: Reticle's `check`/`uncheck` actions on React-controlled checkboxes and radios are setting the DOM's `checked` property directly, bypassing React's `onChange` event. This leads to a discrepancy between the DOM and React's state, resulting in a "false green" where Reticle reports success and the DOM appears updated, but the application's state remains unchanged. This issue has been reported independently on different applications and affects both checkboxes and radio buttons.

AI Summary: The agent incorrectly reports that no development server is listening on specified ports when the server is bound to wildcard addresses (0.0.0.0 or [::]) on Windows. This leads to misleading error messages, causing users to take incorrect troubleshooting steps and potentially abandon the setup process.

AI Summary: A strict Content-Security-Policy (CSP) in Next.js applications is silently blocking the agent's bridge WebSocket connection, leading to installation failures that are not detected by existing `init`, `status`, or `doctor` checks. The issue requires adding CSP validation to the installation process to detect and report the specific `connect-src` directive needed.

AI Summary: The issue reports that 'atoms' in the `eo-runtime` are incorrectly included in lcov coverage reports, despite being inherently unexecutable and thus unable to achieve coverage. The proposed solution is to exclude lines corresponding to atoms from the generated `.lcov` file.

AI Summary: The agent incorrectly flags 3xx redirects, commonly used in login flows, as failed requests. This happens because the fetch network observer treats any 3xx status as a failure, while the XHR observer correctly identifies them as successful redirects. This bug prevents standard login flows from receiving a clean 'verified: true' verdict.

AI Summary: The Vite plugin for Reticle currently does not expose the `allowNonLocalhost` option, preventing host-based multi-tenant applications from integrating with Reticle. This is a critical issue as these applications cannot be served on localhost and the plugin's injected `connect()` call does not support passing this necessary option.

AI Summary: The `reticle gate` command incorrectly reports 100% coverage and a passing status when a project has no recorded flows. This is misleading as it suggests verification has occurred when, in fact, nothing was checked. The suggested fix is to either omit the coverage percentage or return a distinct 'no_flows' status instead of a 'pass: true' when there are no flows to cover.

AI Summary: This feature request aims to enhance the `forge pr create` command to automatically push the current branch to the remote repository if it doesn't already exist upstream. This would prevent cryptic GitHub errors and streamline the pull request creation process, similar to how `gh pr create` behaves.

AI Summary: This issue proposes adding a generalized commit reference resolution mechanism that works across different forges like GitHub, GitLab, and Gitea/Forgejo. Currently, only GitHub has this capability. The goal is to define a common interface for resolving branch names, tags, and abbreviated SHAs to full commit SHAs, ensuring consistent behavior and error handling across all supported forges.

AI Summary: This issue reports the results of a link checker run, identifying 7 broken links across two files. The majority of errors are 404s from datakitchen.io, with one DNS error from dataoculus.app. The goal is to fix these broken links.

AI Summary: This issue is a beginner-friendly task to add a new fun fact about Japan to a JSON file. It requires no coding and can be completed in under a minute by following simple instructions, making it ideal for first-time contributors and Hacktoberfest participants.

AI Summary: Images within a specific blog post on the Meshery website are not scaling correctly on mobile devices. They overflow the viewport, causing horizontal scrolling and a poor user experience. The expected behavior is for all images to be responsive and fit within the mobile screen.

AI Summary: This is a feature request to add support for VHF/UHF frequencies to the RX-888 device. The user is asking if this functionality is possible or planned.

AI Summary: This issue proposes enhancing the chatbot version details view to include a diff against the previous version, similar to the 'create new version' page. It also suggests the ability to compare any two arbitrary chatbot versions, providing greater transparency into changes.

AI Summary: The coverage ratchet script incorrectly reports a 'baseline_bumped' status even when coverage measurements are identical, solely due to changes in provenance information like head SHA and run ID. This leads to unnecessary pull requests being opened for trivial provenance updates, consuming reviewer time and merge queue slots. The fix needs to align the script's behavior with its documentation regarding when provenance updates should trigger a 'bump' status.

AI Summary: This issue proposes creating a new documentation page to guide contributors on how to review first-time pull requests (PRs) in a kind and constructive manner. The goal is to foster community growth by encouraging experienced contributors to mentor newcomers through the review process, with specific deliverables including a checklist, example comments, and linking to the contributor ladder.

AI Summary: This issue requests an improvement to the CLI's `fit` command by adding help text that clearly demonstrates accepted skill and time values. The goal is to make these options more discoverable for contributors, with specific examples for skills and time formats like '15m', '30m', and '1h'. The changes should be made in `src/cli.ts` and `docs/CLI.md`, with tests in `tests/smoke.test.ts`, ensuring existing functionality remains intact.

AI Summary: This issue requests the addition of a new unit test file (`tests/unit/hbar_unit_test.py`) for the `HbarUnit` enum in the Hiero SDK Python. The goal is to ensure that all members of the enum and the `HbarUnit.from_string()` method, including its error handling, are thoroughly tested to prevent potential bugs in currency conversions.

AI Summary: The user is asking for a way to use namespace names (like 'thesaurus') instead of numbers in mwoffliner, as namespace IDs can vary between languages. This would improve usability by allowing the tool to automatically map names to the correct IDs for different Wikimedia sites.

AI Summary: This issue is a beginner-friendly task to add a new color theme named "Sakurajima Ash" to the KanaDojo project. It requires no coding and can be completed entirely in the browser by editing a JSON file. The contribution involves forking the repository, adding the theme's details to a specific JSON file, and submitting a pull request.

AI Summary: This issue proposes implementing smooth scrolling behavior when using the `BringIntoView()` function, commonly used for anchor navigation. The feature should be optional and configurable by the user.

AI Summary: The `get_required_join_uuids` method in `JoinStepCollection` mutates its internal `defaultdict` by adding an empty set for unregistered `JoinStep` objects. This side effect, while currently harmless, could lead to unexpected behavior in the future if a `JoinStep` is queried before being registered. The fix involves changing the lookup to avoid mutation and adding a test to verify this behavior.