Find meaningful ways to contribute

This issue addresses a bug where pull requests modifying GitHub workflow files are incorrectly assigned an "adopt-supersede" decision, leading to an escalation to "needs-decision" due to missing permissions. The fix ensures these workflow-path PRs receive a "capability-gap" rule instead, preventing unnecessary escalations.

This issue reports a stylistic duplication of the 'human-changes-requested' literal string across two Go packages, `prstage` and `stagelabels`. While not a correctness defect, it's flagged for review and should be addressed within the related PR #15256.

This issue requests the implementation of a new Git provider for Bitbucket. It specifically mentions building upon the new structural changes introduced in a recent pull request, indicating a need to integrate with an existing framework.

This issue proposes adding a new configuration setting to the Burrito tool. This setting would prevent Burrito from executing 'apply' operations if the 'plan' output indicates that any resources are scheduled for destruction. The goal is to enhance safety and facilitate adoption on critical Terraform code by preventing accidental resource deletion.

This issue investigates why signals based on 'prior_resistance' levels are performing negatively, as indicated by audit data showing a loss of -$6.46 per pick. The proposal is to restrict signals to 'ATH' (All-Time High) and 'multi-year' levels and to analyze if the negative performance is driven by fallback logic in the `_find_prior_resistance` function.

This issue investigates underperformance of the `has_pole` factor in the top 5 ranked picks, showing negative returns in most backtest windows. The hypothesis suggests that the `_detect_pole` function might be incorrectly identifying recently extended stocks as having a 'pole', rather than the intended pattern of a pole followed by a tight consolidation. Proposed work includes further analysis and testing of modified criteria for the `has_pole` factor.

This issue requests an update to the README.md file to reflect the current paper trading performance. The existing snapshot is outdated and shows a positive result, while the current performance is negative. The proposed changes include replacing the snapshot with current data, summarizing audit findings, clarifying reproducibility, and maintaining a factual tone.

This issue proposes making the audit process reproducible by shipping the analysis script and a snapshot of the simulated trade log. This will allow contributors to verify and extend the audit's findings without needing access to sensitive live account data.

This issue proposes enhancing the paper trading simulator and report to persist crucial trade data like regime, ADR, and risk multiplier. This will enable the generation of detailed diagnostic reports, including P&L by regime, payoff analysis, and exit quality metrics, which were previously computed manually.

This issue proposes changing the 'go-live' gate in a trading scanner from requiring a positive total Profit & Loss (P&L) after 60 trades to using a confidence interval for the mean 'R' (risk-reward ratio). The current method is deemed unreliable due to high noise relative to the expected edge. The proposed change aims to provide a more statistically robust assessment of the trading strategy's performance.

This issue proposes evaluating a reduction in the maximum position percentage (MAX_POSITION_PCT) from 20% to 10-15%. The goal is to prevent low-volatility stocks from dominating the trading book, as current sizing logic leads to larger positions for less volatile names. The proposed work involves comparing different cap percentages using a backtesting harness to analyze performance metrics like dollar per pick, worst 10-day cluster loss, and a max-drawdown proxy.

This issue proposes to modify the signal generation logic to skip signals where the calculated stop loss distance is artificially floored at 3% due to extremely low volatility. This occurs with pinned takeover targets or low-volatility stocks, leading to disproportionately large position sizes that are unlikely to result in profitable breakouts. The change aims to prevent these signals from being generated, improving the quality of trade signals.

This issue proposes to improve the breakout scanner's trading logic by adding confirmation for entries and exits. Currently, orders fill as soon as the price crosses a level, without considering volume or closing price. The proposed changes include exiting trades if the day closes below the entry price or requiring a confirmed close above the level before entering a trade.

This issue proposes a new exit strategy for a trading bot, combining a tight initial stop with an open-ended trailing stop, tested on a volatility-filtered pool of stocks. The current strategy, which uses a fixed 10-day exit, is underperforming due to significant profit leakage and negative post-exit drift. The goal is to capture more of the potential upside by allowing trades to run longer with a trailing stop, rather than being prematurely exited.

This issue proposes to align the backtesting harness's entry logic with the live trading simulator's fill behavior. Currently, backtests enter at the pick-day close, while the simulator uses a more complex level-triggered entry with specific fill conditions. The work involves adding a new backtest entry mode, refactoring fill logic into a shared module, and enhancing reporting to include fill funnel data and R-multiples.

This issue proposes enhancing backtest and paper trading reports to include results in R-multiples and dollar amounts, not just percentages. This is crucial because the live trading strategy uses a dollar-based sizing formula that makes position sizes vary with ATR, a factor currently not reflected in percentage-based reporting. The change aims to provide a more accurate representation of trading performance and decision-making in dollar terms.

This issue describes recurring failures when downloading stock data using the yfinance library, resulting in 50-190 tickers failing on each run. The proposed solution involves setting a project-local cache for yfinance to avoid SQLite database issues, implementing a retry mechanism for failed tickers, and exploring alternative download strategies if errors persist. The goal is to significantly reduce failed tickers and improve download reliability.

The autonomous paper trading bot is underperforming the market due to issues with its payoff structure, position sizing, regime detection, and entry confirmation. The audit identified four primary causes for the bot's losses, which are being addressed through proposed work items related to selection and sizing.

This RFC outlines a roadmap for enhancing vLLM-Omni's full-duplex capabilities, focusing on improving performance, accuracy, and functionality for various models like MiniCPM, JoyAI, and Qwen3-Omni. Key areas include architectural updates for tool calls and multi-replica support, alongside model-specific optimizations for long conversations, speech streaming, and caching mechanisms.

The device boots successfully and displays a splash screen, but then the screen turns black and becomes unreachable by the companion app. Initial logs showed a clean boot, suggesting the issue occurs after the clock UI is created but before the device fully initializes or potentially due to a silent crash.

The RISC-V backend in LLVM crashes when attempting to convert narrow integer vectors (like i2 or i4) to 16-bit floating-point vectors (half or bfloat) using sitofp or uitofp instructions. This occurs due to an internal check in the TargetLowering::isExtFree function, which incorrectly identifies the instruction as not being an extension, leading to an UNREACHABLE state.

This issue identifies overlapping test scenarios in the `automerge_adoption_orphan_test.go` file with existing tests in `automerge_adoption_readopt_journal_test.go`. The goal is to deduplicate these tests later, but it is currently blocked by PR #15206.

A pull request with a workflow change was blocked by a sentinel alert, but a human's "changes requested" review was ignored. The system incorrectly kept the PR in a "needs human" state, even after the review, because the sentinel check happened before the review was processed. The expected behavior is that a human review should override the sentinel alert and correctly route the PR.

This issue describes a bug where the toast notification for an issue decision incorrectly uses Pull Request (PR) terminology like "approved for merge" instead of issue-specific language. Additionally, the notification displays raw timestamps and doesn't clearly explain the underlying reason for the decision not taking effect, which is a lingering label preventing the issue from progressing.

The tracker incorrectly skips the 'Merging' state for pull requests, showing them as 'merged' immediately. This is because the 'merging' state is not explicitly tracked and the UI relies on diffing states between polls, leading to transient states being missed. The fix involves adding a merge-attempt registry on the backend and ensuring the SPA holds the 'Merging' state for a minimum duration.

This issue requests two UI/UX enhancements for the Activity Monitor's merged ledger. First, the animation of a glyph rising to a chip should be slowed down significantly for a more subtle effect. Second, the numerical count should animate like an odometer, with each digit rolling to its new value, with specific conditions for when this animation should occur.

This issue proposes adding a new documentation file, `docs/deploy-vps.md`, to guide users on deploying the application on a VPS using Nginx or Caddy as a reverse proxy, along with a Node.js process manager. The goal is to provide a vendor-neutral deployment solution.

This issue requests the creation of a new documentation file, `docs/deploy-fly.md`, to guide users on deploying the project to Fly.io. The new documentation should leverage the existing Dockerfile and avoid creating a separate image. The task is considered straightforward, with verification involving checking for the file's existence and a link in the README.

This issue requests the addition of a new documentation file, `docs/deploy-railway.md`, to guide users on deploying CloakBin using Railway. The guide should focus on a static/web service path and reference existing environment variables without introducing new adapters.

This issue requests the addition of a unit test for the `/api/health` endpoint. The test should mock the database's health check function to ensure the endpoint returns a 200 status code on success and a 503 status code when the database health check fails.