Help Wanted

AI Summary: This is a beginner-friendly issue asking contributors to add a new anime quote to a JSON file. No coding is required, and the task can be completed directly in the browser within a minute.

AI Summary: This issue aims to integrate existing instrumented tests for the Settings screen into the CI and release workflows. Currently, these tests, which verify a fix for a Settings crash and Compose regressions, are not executed in the required automated checks. The goal is to add an emulator-backed CI job that runs these specific tests before release artifacts are published, ensuring UI regressions are caught.

AI Summary: This issue identifies hardcoded English strings within the `SummaryCards.svelte` component that are not being internationalized. These strings will remain in English regardless of the user's selected language. The fix involves integrating the component with the existing i18n system, similar to a previous resolution for `AgentStatsPanel.svelte`.

AI Summary: This issue highlights discrepancies in the CONTRIBUTING.md file. It incorrectly specifies a 'feature/' branch prefix and lists 'feature' and 'kernel' issue labels that do not exist in the repository. The file needs to be updated to reflect the actual branch naming conventions and existing issue labels.

AI Summary: The documentation in AGENTS.md and BRANCHING.md incorrectly references a non-existent branch-guard hook file path (`.claude/hooks/branch-guard.js`). The actual hook file is located at `.codex/hooks/branch-guard.js`. This issue requires updating the documentation to reflect the correct path or to accurately describe the hook's availability.

AI Summary: This issue highlights inconsistencies in Node.js version requirements across three different documentation files: CONTRIBUTING.md, README.md, and llms-full.txt. The current documentation is contradictory, with the lowest stated requirement (Node.js 18+) being unusable due to dependency constraints, leading to build failures for contributors. The goal is to harmonize these requirements to reflect the actual supported Node.js version (22.x) as indicated by package.json and CI configurations.

AI Summary: This issue highlights several instances where documentation and code counts (like test numbers and file counts) are out of sync and not automatically verified. The `counts:check` gate, while functional for some metrics, doesn't cover these specific discrepancies, leading to stale information in READMEs and other markdown files. The proposed solution is to remove or update these hand-maintained counts to align with the actual state of the repository.

AI Summary: The Vitest configuration file incorrectly points to a non-existent JavaScript file for code coverage reporting. This file has been migrated to TypeScript, causing the toast store module to be silently excluded from coverage reports, leading to under-reporting. The issue requires updating the configuration to reference the correct TypeScript file.

AI Summary: The README's instructions for starting the demo build are incorrect, as `npm run build:demo && npm start` results in the non-demo application being launched. The `build:demo` command correctly builds the demo bundle, but `npm start` then rebuilds the standard renderer and launches Electron without the demo mode enabled. A working alternative is to use `npm run dev` which starts a development server with the demo engine active.

AI Summary: The "Star on GitHub" link in the demo banner incorrectly points to a non-existent GitHub organization ('anthropos17'). The correct organization name is 'antropos17'. This issue requires changing the URL in the `DemoBanner.svelte` component to the correct GitHub repository.

AI Summary: This issue identifies outdated information in the project's documentation regarding filtration filters. Specifically, two paragraphs and a table incorrectly state there are 11 filters, when in fact there are only 9 due to two filters being removed. The fix involves updating the counts and references to reflect the current number of filters.

AI Summary: This issue proposes the removal of an unused function `tanimoto_kernel` and its associated `numpy` import from the `filtering.py` file. The function is no longer called by any other part of the codebase, making its presence redundant. Removing these elements will clean up the code and reduce dependencies.

AI Summary: This issue is a "Good First Issue" designed for absolute beginners to make their first open-source contribution. It involves adding a new Japanese grammar point to a JSON file, requiring no coding or local setup, and can be completed in under a minute directly from the browser.

AI Summary: This feature request proposes adding a smooth, animated transition between list and grid views for a collection of items. The goal is to make layout changes feel less abrupt by visually retaining item identity during the transformation, using a FLIP-style animation. This enhancement aims to improve the user experience by making responsive layout changes more understandable and visually appealing.

AI Summary: This issue questions the inclusion of deques in the Silver Graph Traversal module on usaco.guide, as the provided problems do not seem to necessitate their use. The reporter is seeking clarification on why deques are introduced if they are not a required tool for the module's content.

AI Summary: This issue is a "Good First Issue" designed for absolute beginners to contribute to an open-source project. The task involves adding a new trivia question about Japanese flower arranging (Ikebana) to a JSON file. No coding or repository setup is required, and the contribution can be completed directly in the browser in under a minute.

AI Summary: This issue requests a comprehensive update to the project's documentation regarding the `.ship/config.yaml` schema. The goal is to ensure that all fields within `AppConfig`, `ServerConfig`, and `AIConfig` are fully documented, including their purpose and example values, and that any discrepancies with the current code are resolved. Specific attention should be paid to the `domain` field's SSL interaction and the listing of supported AI providers.

AI Summary: The frontend of the project lacks any automated testing setup, including a test runner and a test script. The proposal is to integrate Vitest and React Testing Library, starting with basic component tests and ensuring CI integration. This issue is suitable for a developer familiar with React but new to the Go aspects of the project.

AI Summary: This issue highlights a critical lack of unit test coverage across most of the Go codebase, particularly in high-risk areas like deployment and configuration loading. The proposal outlines a phased approach to add tests, starting with the most testable and valuable components like configuration handling and AI fallback logic, before tackling more complex, I/O-bound modules.

AI Summary: This issue proposes adding code formatting and linting checks to the CI pipeline for Go projects. Currently, the CI only builds and vets the code, allowing unformatted or problematic code to merge. The fix involves adding `gofmt -l` and optionally `golangci-lint` to the CI workflow.

AI Summary: The CI pipeline is not failing the Pull Request when frontend linting errors occur due to `continue-on-error: true` being set on the linting step. This issue proposes removing that setting after existing lint errors are resolved, ensuring CI correctly flags these issues and blocks PRs.

AI Summary: This issue proposes adding support for a `.shipignore` file, similar to `.gitignore`, to allow users to specify custom directories and files to exclude during project uploads. The implementation should merge user-defined patterns with the existing hardcoded excludes and gracefully fall back to the default behavior if no `.shipignore` file is present. This enhancement aims to provide greater flexibility for users in managing their uploads.

AI Summary: This issue proposes adding a pre-check to ensure a domain's DNS records correctly point to the server before attempting to obtain an SSL certificate. This prevents common first-time user errors, rate limiting, and provides clear guidance to the user on how to fix the DNS issue.

AI Summary: The current deployment process generates Nginx configurations that reference SSL certificates which are never actually obtained. This leads to Nginx failing to start on deployments with SSL enabled and a domain configured. The proposed solution involves integrating Certbot into the deployment flow to obtain certificates before applying the SSL configuration, ensuring a fallback to HTTP-only if issuance fails.

AI Summary: This feature request proposes adding an animated visual cue to data cells that update dynamically. When a cell's value changes, it should briefly highlight and its new value should animate with a subtle scale/fade transition. This aims to improve user attention to data changes in dashboards and data tables without complex layout animations.

AI Summary: An issue exists where ACP-based agents incorrectly display raw protocol identifiers like `usage_update`, `session_info_update`, and `available_commands_update` as status messages in the chat transcript. This happens because the client application doesn't have specific handlers for these stabilized ACP notifications, causing them to be forwarded as generic status events.

AI Summary: The Ava browser is not correctly applying kiosk mode when the Browser URL includes query parameters like 'kiosk' or 'hide_header'. The issue appears to be that these query parameters are being stripped from the URL before the kiosk mode functionality can be activated.

AI Summary: This issue requests the addition of a new page to the web UI dedicated to downloading CLI packages. The page should clearly present various CLI options, differentiating between Java and native binaries, and provide platform-specific download links or installation instructions. A prominent link to this new page needs to be added within the existing web UI.

AI Summary: This issue reports that Mellom appears to have new pricing, with updated pages observed on August 20th. The exact effective date of these prices is unclear, but the reporter speculates it could be August 1st or September 1st.

AI Summary: The "Node input" component in the frontend currently only shows tag suggestions after a user types characters. This enhancement aims to display the full list of available tags immediately when the component is focused, improving user experience by making all options visible upfront.