🚀🧑‍💻 - 3.10.6 - Release from develop #765

Release Type

Patch

Release Version

3.10.6

Changelog

• Prevent workflow predecessor deadlocks on shared runners and coalesce queued issue admission before allocating full runner jobs (🐛🧑‍💻 - Runtime predecessor queue can deadlock per PR workflows on shared runners #692, 🐛🧑‍💻 - Coalesce repeated issue admission events before allocating complete runner jobs #730).
• Improve pre-branch SDD validation, catalog compatibility, blocked preparation diagnostics, and safe recovery guidance (🐛🧑‍💻 - Expose blocked pre branch SDD outcomes and safe recoverable draft diagnostics #714, 🐛🧑‍💻 - Pre branch SDD crashes on a valid repository native capability catalog #716).
• Preserve complete review conversations and explicitly reopened findings; ground Bugbot findings and suggested fixes in framework behavior, versioned upstream contracts, typed fault evidence, and exact validation counterexamples (🐛🧑‍💻 - Reopened dismissed Bugbot finding remains verification required after copilot recheck and blocks guarded approval #700, 🐛🧑‍💻 - PR review confuses Compose width with requiredWidth suggested modifier order removes width cap #720, 🐛🧑‍💻 - PR review rejects valid official android 37.0 package and recommends an absent SDK ID #721, 🐛🧑‍💻 - PR review misses ComposeViewport owned cleanup and falsely reports a permanent loading screen #722, 🐛🧑‍💻 - Automated Codecov User reports incorrectly make complete diff review context partial #724, 🐛🧑‍💻 - Bugbot misidentifies Exposed SQLException inheritance despite compiled artifact and real SQL fault evidence #736, 🐛🧑‍💻 - Bugbot predicts failing test despite indirect participant binding and passing typed fault assertion #738, 🐛🧑‍💻 - Bugbot recommends an undeclared setup dart input despite the versioned upstream contract #739, 🐛🧑‍💻 - Bugbot claims an already rejected empty email domain label is accepted exact Unicode counterexample #749).
• Explain rejected comment commands and consumer issue admission failures with actionable validation and recovery details (🐛🧑‍💻 - Explain rejected comment command input with actionable validation errors #701, 🐛🧑‍💻 - Consumer bug form version heading disagrees with admission catalog and hides recovery details #725).
• Keep progress assessment within issue acceptance scope and recover complete immutable comparison evidence, including large comparisons and inherited binary baselines (🐛🧑‍💻 - Progress assessment turns separate debt and excluded device tests into completion requirements #717, 🐛🧑‍💻 - Support complete immutable evidence for large comparisons with omitted GitHub patches #726, 🐛🧑‍💻 - Progress assessment fails permanently on inherited binary files without GitHub textual patches #727).
• Prepare verification dependencies from the correct candidate workspace, preserve authoritative issue/branch relationships, and report partial reconciliation and optional check publication failures precisely (🐛🧑‍💻 - Commit size reconciliation fails after partial effects with opaque provider.unavailable diagnostics #718, 🐛🧑‍💻 - bug contextual PR issue mentions produce unrelated Branch synchronized cards #723, 🐛🧑‍💻 - Optional Check Run publication fails without actionable diagnostics in the commit workflow #728, 🐛🧑‍💻 - sync branch prepares dependencies on the wrong workspace revision and hides missing packages behind workflow.failed #746).
• Support safe replacement of unpublished release/hotfix candidates and preserve the explicit launcher issue during tag-push publication finalization (🐛🧑‍💻 - No supported recovery for an unpublished candidate when promotion PR CI requires a source fix #732, 🐛🧑‍💻 - Tag push createrelease loses the explicit Action issue and blocks finalization after all packages publish #740).
• Include the browser extension product specifications, portable workspace/build foundation, and protected browser runtime/read-session infrastructure merged into develop (✨🧑‍💻 - Specify a cross browser GitHub extension usability features MVP and Action integration #694, ✨🧑‍💻 - Browser extension H1 portable workspace target builds and architecture gates #702, ✨🧑‍💻 - Browser extension H2 browser runtime lifecycle protected sessions and actual browser harnesses #703).

Additional Context

The maintainer requested a patch release from develop. Latest published stable release: v3.10.5. Next patch: 3.10.6.

Use the installed Action-managed release lifecycle and freeze the current develop snapshot. At request preparation, develop is 4f69a8f; the Action must record the exact origin SHA when cutting the release. Later development commits are outside this release.

Prepare the version and compiled artifacts on the Action-owned release branch, run the configured validation and package smoke checks, and promote through the protected production PR before publication. Retain the production ancestry from v3.10.5, whose SDD correction is already represented in develop through #695/#696. Complete the normal development reconciliation after publication.

Verify the immutable v3.10.6 tag, npm @vypdev/copilot@3.10.6 version/gitHead, GitHub Release, moving v3 Action reference, and durable operation against the accepted production SHA. Do not bypass protected checks or create replacement refs manually.