Help Wanted

AI Summary: This issue proposes enhancing the `attendees` property to accept a list of email strings directly, rather than requiring them to be formatted as `vCalAddress` objects. The goal is to simplify the developer experience by allowing straightforward email input, with a TDD approach outlined for implementation and testing.

AI Summary: This issue requests the addition of new tutorials to the documentation. These tutorials should focus on demonstrating the usage of the new models and API features introduced in version 2 of the project.

AI Summary: This issue requests an update to the `tslib` tutorial for version 2 of the library. The current tutorial is outdated and does not reflect recent changes, specifically the use of `pkg` classes. The goal is to bring the tutorial in line with the latest version of the library.

AI Summary: This issue requests the addition of a new Japanese cultural etiquette tip regarding photography in temples and shrines. The contribution involves editing a JSON file directly in the browser, requiring no coding or local setup, and is designed for absolute beginners.

AI Summary: This issue proposes a "Neon Pulse Ring" component, a visually engaging radial breathing glow ring with a ripple trail. It aims to provide interactive effects on hover and click, with optional cursor tracking, primarily using CSS for animations. The goal is to create a unique, animation-first component suitable for various UI elements.

AI Summary: This issue aims to improve the security of the `loop-action` command invocation within GitHub Actions. The goal is to prevent unquoted expansion of the `inputs.command` variable, which can lead to unexpected behavior with multi-argument or multi-line commands. The solution involves ensuring commands are safely quoted or executed in a more robust shell environment, with documentation updates to reflect safe usage and warnings against untrusted input.

AI Summary: This issue requests contributors to share a real-world production story about using a 'CI Sweeper' tool, focusing on either successes or, preferably, failures. The story should be documented in a new Markdown file and include specific details about the pattern, tools used, a failure or surprise, and an actionable lesson learned, while avoiding sensitive information.

AI Summary: This issue proposes adding a new subsection to the QUICKSTART documentation to explain the 'loop-gate' functionality. The goal is to make the denylist and auto-merge allowlist features discoverable alongside the `gate.yaml` file, providing clear instructions and examples for their usage.

AI Summary: This issue requests the addition of a new subsection about `loop-sandbox` to the `QUICKSTART.md` documentation. The goal is to introduce newcomers to this package, which is used by `loop-action` but might be overlooked by those only familiar with `audit` and `init`. The new section should explain its ephemeral worktree isolation, provide usage examples, and link to relevant safety information.

AI Summary: This issue requests the addition of a new subsection to the QUICKSTART documentation to introduce the `loop-action` composite action. The goal is to make this new action easily discoverable by CI adopters, providing clear instructions on its usage, inputs, and best practices within GitHub Actions workflows.

AI Summary: This issue proposes adding a new example document to the Hermes project that demonstrates an "Issue Triage" pattern. The goal is to expand Hermes' capabilities beyond its current "daily triage" pattern by providing a concrete example of how to handle issue triage using Hermes.

AI Summary: This issue requests the addition of a new example documentation for the Hermes CI Sweeper. The new example will demonstrate how to classify failures, update states, and map cron jobs or event triggers, with a focus on report-only functionality for the first week and verifier/worktree notes for the second. The goal is to expand Hermes' documentation beyond its existing Daily Triage and PR Babysitter examples.

AI Summary: This issue requests the addition of a new example documentation for the "Windsurf Dependency Sweeper". The task involves creating a new markdown file for the example, linking it from the Windsurf README, and updating a coverage table in the main examples README. The goal is to fill a gap in the documentation coverage.

AI Summary: This issue requests the creation of a new documentation example for "Windsurf Issue Triage". The goal is to fill a gap in pattern coverage by adding a markdown file that demonstrates how to triage issues within the Windsurf context. The work involves creating a new markdown file, linking it in the Windsurf README, and updating the main README to reflect the new example.

AI Summary: This issue requests the addition of a new example documentation for the Windsurf CI Sweeper. The goal is to fill a gap in the pattern coverage table and provide a clear example for Windsurf users, similar to existing examples for Cursor and Opencode. The work involves creating a new markdown file, linking it in the Windsurf README, and updating a master README table.

AI Summary: This issue describes a limitation in the GumTree code comparison tool where it fails to correctly match changes within comma-separated lists. Specifically, adding a new element to such a list is not accurately detected by GumTree, leading to incorrect diffs. The problem is demonstrated with three examples from the Hyprland project.

AI Summary: This issue addresses missing documentation for several parameters (`links`, `related_to`, `refids`, `concepts`) across three factory methods of the `Alarm` class. These parameters are accepted but not mentioned in the docstrings, making them discoverable only through `Alarm.new()`. The goal is to add these parameters to the documentation of `new_audio` and `new_email` to ensure consistency and discoverability.

AI Summary: This issue proposes optimizing the `convert_html_tables` function by caching repeated calls to `find_all('tr')` within table processing. The current implementation unnecessarily re-scans table rows multiple times, leading to minor performance inefficiencies. The suggested fix involves hoisting the row finding operation to a single point and passing the results to relevant handler functions.

AI Summary: This issue is a beginner-friendly task to add a new Japanese video game quote from Persona 5 Strikers to a JSON file. No coding is required, and the contribution can be made directly through the browser in under a minute.

AI Summary: This issue proposes two minor improvements to the node-wot interop README. First, it suggests removing the unnecessary `npm init -y` command, which creates an unused package.json file. Second, it recommends updating the tool name separator from '.' to '__' for consistency.

AI Summary: This issue aims to improve test coverage for the `send_with_retry` function in `src/thingctx/reliability.py`. Specifically, it requires adding tests for scenarios where the transport fails and for handling `retry_after` when no response is received.

AI Summary: This issue requests the addition of unit tests to cover specific error conditions and a particular code branch related to ISO 8601 date parsing within the `contrib/time.py` file. The goal is to improve test coverage for these identified scenarios in the `src/thingctx/contrib/time.py` module.

AI Summary: This issue requests adding unit tests to the `lint.py` file in the `thingctx` repository. Specifically, tests are needed for the rule that flags when a description is identical to the affordance name, and for the `LintFinding.as_dict()` method. Both are described as pure functions operating on dictionaries.

AI Summary: This issue proposes adding tests to the gateway binding conformance kit within the `thingctx.testing` module. Currently, the conformance kit, designed to verify third-party bindings, lacks its own tests for the gateway binding component, leaving it unchecked. The estimated effort for this task is approximately 2 hours.

AI Summary: This issue proposes adding a new "sysinfo" handler for the `local://` protocol. This handler would provide basic host information like platform, CPU count, and disk free space, without requiring any external dependencies. It aims to be similar in structure to the existing `time` handler and is estimated to take around 3 hours to implement.

AI Summary: This issue aims to add the `examples/05_oauth2.py` script to the existing examples smoke test. This will prevent the OAuth2 example from becoming outdated and silently breaking without detection. The focus is on ensuring the example code remains functional, not on testing the underlying OAuth2 feature itself.

AI Summary: This issue requests updating the `examples/README.md` file to include links to the `examples/interop/` and `examples/oauth_connect/` directories. Currently, these directories are not indexed, making their content discoverable only by browsing the file tree. The estimated time to complete this task is approximately one hour.

AI Summary: This issue requests documentation for several trust flags (`--approve-when`, `-y`/`--yes`, and `THINGCTX_APPROVE_WHEN`) within the `USAGE.md` file. These flags control whether destructive actions require human confirmation. The estimated effort for this task is approximately one hour.

AI Summary: This issue requests that the `thingctx auth login` command display user-friendly CLI flag names in its missing configuration error messages, instead of internal configuration keys. The goal is to make it easier for users at the terminal to understand how to resolve the error by providing the correct flag.

AI Summary: The `thingctx lint` and `thingctx import openapi` commands currently crash with an unhandled traceback if the specified OpenAPI file is missing or not valid JSON. This issue proposes to handle these errors gracefully by providing informative messages to the user instead of a traceback, improving the user experience for common mistakes.