Help Wanted

AI Summary: This issue requests the addition of a new animated UI component for visualizing quantum teleportation within a noisy intermediate-scale quantum (NISQ) era context. The component requires ultra-complex rendering with specific visual elements like flux rotation, boundary tracks, and telemetry controls, along with semantic HTML and advanced CSS for animations and gradients.

AI Summary: This issue requests that the comment box for license risks be visually updated to match the appearance of the comment box for dependency risks. The goal is to achieve visual consistency across different risk types within the application.

AI Summary: This issue announces a volunteer sprint for the Clarvia non-profit, which provides bereavement guidance. It invites teams of developers, designers, and PMs to sign up by commenting with their team name, roles, availability, and desired starter issues. Several starter issues are listed across different roles, focusing on tasks like data capture, design, accessibility, documentation, and content.

AI Summary: Timestamp fields in Drizzle with `mode: 'date'` are causing validation errors in ts-rest. This is because Drizzle returns `Date` objects, but `JSON.stringify` converts them to strings, leading to mismatches between server-side type expectations and client-side runtime validation. The proposed fix involves overriding these fields in the schema to accept both `Date` objects and ISO strings.

AI Summary: The scaffolded `NEXT_PUBLIC_API_BASE_URL` in the full-stack application is missing the global API route prefix, causing hooks to 404 when making requests to the actual API. The fix involves updating the scaffolded environment variable to include the `/api` prefix, ensuring consistency between the web client and the API server.

AI Summary: This issue requests the removal of unnecessary right-side padding on the mentor dashboard. The fix involves conditionally removing a CSS class (`.is-dash-board`) from a specific HTML element when a mentor or administrator is logged in, targeting line 13 of the `bootcamp/app/views/home/index.html.slim` file.

AI Summary: This issue requests the addition of a highly complex, animated UI component demonstrating quantum teleportation using silicon spin qubits. The component requires detailed HTML structure, advanced CSS with specific visual effects, and a comprehensive README file to meet a substantial line count requirement.

AI Summary: This issue proposes adding a new row of commonly used symbols above the software keyboard to improve the typing experience for Markdown code. This enhancement aims to reduce the need for users to frequently switch between keyboard layouts when inputting Markdown.

AI Summary: The `apps/api` scaffold in the full-stack application template fails to enable CORS, causing browser-based requests from `apps/web` to be blocked. This prevents proper local development and end-to-end testing of API integrations. The fix involves adding `app.enableCors()` to the API's bootstrap process to allow requests from the web application's origin.

AI Summary: A Turbopack issue in a Next.js application prevents it from resolving relative imports with `.js` extensions across pnpm workspace packages when `nodenext` module resolution is used. This occurs because Turbopack doesn't support aliasing extensions like webpack does, leading to runtime errors when importing TypeScript files from other workspace packages.

AI Summary: This issue proposes adding a new UI component to display a retro Nixie tube clock. The goal is to create an authentic vintage aesthetic with glowing orange digits, glass tube envelopes, and animated effects like blinking colons and cathode flicker, all implemented using pure CSS for mobile responsiveness.

AI Summary: This issue requests the addition of a command glossary to the `oss-lab` CLI documentation. The goal is to clearly explain the purpose and usage of key commands like `check --profile beginner`, `check --profile maintainer`, and `issues`, including a short example for each. No code changes are expected unless documentation reveals a CLI gap.

AI Summary: This issue proposes adding examples to the documentation on how to use GitHub issue filters. The goal is to help new contributors easily find open tasks by filtering for labels like 'good first issue' and 'help wanted', as well as by issue state and assignee status. This will make it simpler for newcomers to get involved without needing to ask for guidance.

AI Summary: This issue proposes creating a guide to help new contributors reproduce bugs before submitting pull requests. The guide will be added to the documentation and linked from the CONTRIBUTING.md file, aiming to improve the quality of bug reports and streamline the review process.

AI Summary: This issue proposes adding a new `profiles` command to the CLI tool. This command will list the available contributor profiles (beginner and maintainer) and provide a brief explanation of when to use each. The goal is to make these profiles more discoverable to users.

AI Summary: This issue proposes the creation of a visually engaging "Quantum Particle Matrix Loader" component for web applications, specifically targeting complex states in Web3 and AI. The goal is to replace basic spinners with a GPU-accelerated, pure CSS animation featuring orbiting particles, a glowing core, and a progress bar with telemetry text.

AI Summary: The issue describes a bug where a warning icon for over 100 unconfirmed daily reports is not displaying correctly on the dashboard. The reporter has identified that changing a specific `<i>` tag to `<i class="fa-solid fa-triangle-exclamation"></i>` resolves the problem. This suggests a visual display issue related to the icon's class.

AI Summary: This issue describes two problems encountered in a full-stack application. First, the landing page's "Get started" button was a dead CTA with no destination, a runtime/UX issue not caught by build-time checks. Second, `nodenext`-style barrel imports in the `packages/hooks` directory fail to resolve under Turbopack when a real value is imported from a workspace package, leading to runtime errors.

AI Summary: The 'Select User By Email' dropdown on the Pathway Assignments page is not populating with registered users. This prevents administrators from filtering assignments by user email, rendering the user-based search functionality unusable.

AI Summary: This issue describes a mismatch between the dependency constraints defined in `eslint-base.js` and the actual project structure compiled by `core.yaml`. This discrepancy causes linting failures for various layers, including services, APIs, contracts, and hooks, due to incorrect assumptions about library tagging and allowed dependencies. The `enforceBuildableLibDependency` rule also triggers unexpectedly for source-only packages.

AI Summary: The default configuration for the shipped screen layer in the full-stack-app template incorrectly includes mobile-specific testing commands and scopes, even when the mobile add-on is disabled. This leads to build failures on projects without mobile support. The issue requires the template to dynamically adjust its configuration based on the `addons.yaml` file.

AI Summary: The current project structure allows services and controllers to directly instantiate concrete adapters, bypassing the intended port abstraction. This is currently only enforced by code review convention and is not mechanically checked by linting rules, posing a scalability risk as the project grows. The proposed solution involves tightening dependency constraints or adding explicit linting rules to enforce the port discipline.

AI Summary: The `hedgehog verify` command fails to commit newly scaffolded package files (like `package.json` or `tsconfig.json`) when a layer is the first to create its own package and its scope glob doesn't include these files. This leads to an incomplete Git history, where cloned repositories might lack essential build configuration files.

AI Summary: This issue requires updating documentation and internationalization strings to reflect the addition of the `--format sarif` option for `ocr review` and `ocr scan` commands. It also involves adding a GitHub Actions example to demonstrate how to use the SARIF output for code scanning.

AI Summary: This issue requests a calm, single-page print layout (PDF or Figma) for Luxembourg families outlining high-level steps to take in the first 24 hours after a death. The design should be visually appealing, avoid legal advice, and cite official sources for verification, with no unsourced deadlines.

AI Summary: This issue requests a plain-language review and rewrite of English text within the `apps/web/` directory, specifically focusing on the checklist introduction, empty states, and soft error/guidance messages. The goal is to make the copy warm, direct, and easy to understand for families who may be arriving stressed, avoiding overly clever or clinical language.

AI Summary: This issue proposes the creation of a "first hour" contributor guide for new volunteers to the clarvia-org monorepo. The guide will outline three distinct contribution paths: no-code source capture, developing the website (`apps/web`), and drafting graph YAML records, with specific instructions for each. The goal is to simplify onboarding for new contributors and "Good First Issue" teams.

AI Summary: This issue requests an audit of the keyboard and screen reader accessibility for the checklist and contribute pages on the Clarvia website. The goal is to identify and report any accessibility barriers, such as missing labels, focus traps, or poor heading order, and potentially implement fixes.

AI Summary: A volunteer-run bereavement nonprofit is seeking a designer to establish a cohesive visual identity for their website and brand. They need recommendations for a color palette, typography, visual tone, and a new logo to convey calmness, trustworthiness, and dignity during a difficult time for users.

AI Summary: This issue proposes removing unnecessary transparent padding from specific unit images (Knight, Fire, Skeletal Dragon) in the game. The padding is currently used as a workaround for positioning, but it causes issues in other contexts. The suggested solution is to remove the padding from the image files and utilize a new `[default_frame]` tag to manage offsets, as demonstrated by an example.