Help Wanted

AI Summary: This issue proposes to refactor the Agent dashboard to aggregate multiple instances of the same agent type into a single card. Instead of showing individual process cards, similar agents will be grouped, displaying a count and the most severe status among them. Expanding the group card will reveal details of each individual process.

AI Summary: This issue requires unifying the icon used for the 'Push image' action. Currently, the hamburger menu uses `faArrowUp` while the modal uses `faCircleArrowUp`. The task is to change the hamburger menu icon to `faCircleArrowUp` to ensure consistency.

AI Summary: This issue requires updating placeholder icons within the Load, Import, and Save modals to match their corresponding toolbar icons. The specific icon changes are outlined, with a dependency on another issue for the Import icon fix.

AI Summary: The `ptc` command's root usage message does not advertise the `ptc help` command, despite documentation and generated files instructing users to start with it. This omission creates friction for new users and contradicts existing guidance.

AI Summary: This issue addresses a visual conflict on the Images page where both the 'Pull' and 'Import' actions use the same icon, `faArrowCircleDown`. The proposed solution is to change the icons to `faCloudDownload` for 'Pull' and `faCircleArrowDown` for 'Import' to differentiate them visually. This change will be implemented in the `ImagesList.svelte` file.

AI Summary: The Columns widget needs to be made responsive. Currently, on desktop, two columns appear in a single row. The goal is to have these columns stack into two separate rows on mobile devices.

AI Summary: This issue is a beginner-friendly task to add a new color theme called "Night Market" to the KanaDojo project. It requires no coding knowledge and can be completed entirely through the browser by editing a JSON file and submitting a pull request.

AI Summary: This issue is a "Good First Issue" that requests the addition of a new Japanese cultural etiquette tip to a JSON file. The tip focuses on the proper use of chopsticks, specifically advising to use a chopstick rest and avoid sticking chopsticks into rice, as the latter is associated with funeral rites. No coding is required, and the contribution can be made directly from the browser.

AI Summary: This issue highlights documentation gaps for Cogeto contributors, specifically around fast development workflows. It details the lack of clear instructions for running single test files, the convention for frontend tests using jsdom, and the process for using the frontend development server. Addressing these would significantly improve the developer experience.

AI Summary: This issue requires a native French speaker to correct inconsistent terminology within the application's French locale. The word 'scope' is currently translated as 'perimetre' in some files, while the project's glossary and most of the interface use 'portee'. The fix involves updating all instances of 'perimetre' to 'portee' and ensuring the surrounding sentences remain natural.

AI Summary: This issue requires a native German speaker to ensure consistent terminology across the application's German locale files. Three specific terms – 'receipt', 'sensitive', and 'scope' – are currently translated in multiple ways, contradicting the project's glossary. The goal is to unify these translations to a single, glossary-approved term for each, ensuring consistency across both web and server-side locale files.

AI Summary: This issue addresses terminology and grammar inconsistencies in the Croatian locale for the Cogeto application. It requires a native Croatian speaker to standardize the translation for 'scope' to 'doseg', fix three specific grammatical errors related to declension and pronoun capitalization, and ensure proper pluralization for certain phrases. The goal is to improve the naturalness and accuracy of the Croatian user interface.

AI Summary: The chat view's citation rendering component is inefficiently rescanning fact lists for every citation chip on every streaming token. This issue proposes optimizing these lookups by using Maps instead of linear scans, which should make per-chip operations O(1) and significantly improve performance during answer streaming without altering the rendered output.

AI Summary: This issue describes a bug where keyboard focus can escape from open dialogs and drawers into the content behind them. This violates accessibility standards, particularly for users relying on keyboard navigation or screen readers. The fix involves implementing focus trapping for Tab key events and making the background content inert, ensuring a truly modal experience.

AI Summary: This issue identifies two accessibility defects in the Cogeto web interface related to screen readers. First, the unread indicator dot in the navigation is not properly announced due to an incorrect `aria-label` implementation. Second, decorative SVG icons in the navigation and chat pages are announced by screen readers because they lack the `aria-hidden` attribute. The proposed solutions involve correcting the `aria-label` for the unread indicator and adding `aria-hidden` to the decorative icons.

AI Summary: This issue identifies several accessibility problems in the Cogeto web interface, specifically regarding filter inputs and data tables. Filter controls lack accessible names, making them difficult for screen reader users to understand their purpose. Data tables are missing header scope declarations, leading to a confusing reading experience for assistive technologies. The goal is to add programmatic labels to inputs and ensure data tables have proper header scoping and captions.

AI Summary: This issue addresses a usability and accessibility problem where all browser tabs display the same title, making it difficult to distinguish between different pages. The fix involves updating the `document.title` dynamically based on the current page's translated title, which is already available within the application. This change will improve navigation for users with multiple tabs open and for screen reader users.

AI Summary: This issue proposes adding fixture-driven unit tests for a custom, dependency-free ZIP parser used in Cogeto's bulk import feature. The goal is to improve the robustness of the parser by explicitly testing various happy paths, malformed inputs, and edge cases, preventing potential vulnerabilities and ensuring stability when handling user-uploaded files.

AI Summary: This issue requests the addition of unit tests for a locale-aware formatting module in a React SPA. The module handles date, number, percentage, and file size formatting across multiple languages. The tests should cover each exported function, include assertions for non-English locales, and address specific boundary cases for file size and relative time formatting.

AI Summary: This issue requests the addition of unit tests for a pure helper function in Cogeto that scrubs sensitive model output from error messages before logging. The tests should cover various scenarios, including Zod message scrubbing, message length capping, and handling of non-Error inputs, to ensure the privacy guarantee of the system.

AI Summary: This issue identifies duplicated, hand-rolled body validation logic in several API controllers that bypasses a shared Zod validation helper. The goal is to refactor these routes to use the shared helper, improving error message detail and consistency across the codebase. The scope is limited to specific controllers, and existing tests should remain passing.

AI Summary: The Cogeto API's inspection routes for sources currently accept an unvalidated `sourceType` parameter, unlike the sibling list route which validates it. This inconsistency violates the codebase's "Zod at every boundary" rule and can lead to less helpful error messages. The fix involves adding validation to the inspection routes to ensure only registered source types are accepted, mirroring the behavior of the list route.

AI Summary: The data-export endpoint (`POST /api/passport/exports`) incorrectly returns a 500 Internal Server Error for invalid JSON request bodies. This issue should be fixed to return a 400 Bad Request error that clearly indicates the specific validation failure, similar to other endpoints in the codebase. A regression test should also be added to cover this scenario.

AI Summary: This issue aims to replace live GitHub API calls in the `TestGetGitHubRewards` unit test with a mocked server or deterministic offline data. The current test relies on live network requests, causing it to time out in the test harness. This change is part of a larger effort to improve testing reliability.

AI Summary: This issue aims to fix a deterministic test failure in `TestServer_HandleSettingsAll`. The failure occurs because the test incorrectly pre-creates an empty keyfile, causing error handling to trigger instead of the intended key generation logic. The proposed solution is to modify the test to use an unused path within the temporary directory, allowing the code to properly generate the keyfile.

AI Summary: This issue aims to improve code coverage for the `pkg/api/handlers/mcp` package, which currently stands at approximately 51.2%. The focus is on adding targeted tests to cover remaining low-coverage branches, rather than a large-scale refactoring. This is a follow-up task related to a larger issue (#22613).

AI Summary: This issue aims to improve the reliability of nightly end-to-end tests for the GitHub API handler by replacing live API calls with mocked responses. The current tests are failing due to timeouts caused by numerous unauthenticated live API requests, and this change will use `httptest.Server` or an established test pattern to simulate the GitHub API.

AI Summary: This issue aims to improve unit test coverage for the `pkg/agent/providers` module, which currently has low coverage (~44.6%). The focus will be on adding targeted tests for error and edge cases, following existing provider patterns, and keeping the changes small and incremental as part of a larger effort.

AI Summary: This issue proposes the removal of support for Spark-33, which is now deprecated. The tasks involve migrating relevant tests to newer Spark versions, deleting Spark-33 specific tests and code, and cleaning up build scripts.

AI Summary: This issue proposes skipping the Helm test for automated release pull requests. The current CI setup attempts to pull an image that doesn't exist yet during these PRs, causing the test to fail. By skipping this specific test for these PRs, the release process can proceed without interruption.