🚀🧑‍💻 - 3.10.7 - Release #825

Release Type

Patch

Release Version

3.10.7

Changelog

• SDD catalogs and preparation: preserve nested specification directories and accepted filename destinations; publish catalogs without following links or overwriting aliases; reject incomplete symlink discovery; support truthful proposed-capability bootstrap and actionable legacy/missing-trusted-catalog recovery; render accepted capability titles as literal text. References: 🐛🧑‍💻 - bug SDD catalog links discard nested specification directories #768, 🐛🧑‍💻 - bug portable SDD catalog generation follows symlinks outside the repository #771, 🐛🧑‍💻 - SDK proposed capability catalogs have no truthful greenfield SDD bootstrap route without implementation evidence #777, 🐛🧑‍💻 - Branch sync rejects legacy evidence catalogs as evidence shape before compatibility diagnosis #779, 🐛🧑‍💻 - Portable SDD catalog renders accepted parenthesis paths as broken Markdown links #782, 🐛 - Fix path handling in canonical SDK catalog generation nested links and output symlinks #789, 🐛🧑‍💻 - SDD catalog discovery silently skips unregistered specification symlinks #804, 🐛🧑‍💻 - Pre branch SDD missing trusted catalog is hidden behind generic workflow.failed and retry guidance #808, 🐛🧑‍💻 - Accepted capability titles inject Markdown structure into generated SDD catalogs #820.
• Review grounding and regressions: improve evidence for Kotlin/Wasm bindings, same-repository Action references, relative SDD links, dependency-generated transport values, generated-source coverage coordinates, initial browser-session credentials, unittest discovery, Kotlin Json policy and Ktor routing-root identity. Preserve genuine-defect controls and distinguish source/runtime evidence. References: 🐛🧑‍💻 - Bugbot false positive KotlinWasm js parameters are valid generated JavaScript bindings #764, 🐛🧑‍💻 - Bugbot rejects documented checkout free self repository Action references that already ran successfully #770, 🐛🧑‍💻 - bug review misresolves valid relative SDD links and persists false broken path findings #772, 🐛🧑‍💻 - Bugbot flags a missing Coil no store header despite passing real transport tests #784, 🐛🧑‍💻 - Bugbot confuses generated Kotlin source lines and flags correct JaCoCo missed line assertions #796, 🐛🧑‍💻 - Bugbot attributes an initial JWT session to an unused token response stub and flags passing browser assertions #798, 🐛🧑‍💻 - Review claims a unittest module never runs despite wildcard discovery and actual CI execution #806, 🐛🧑‍💻 - Review false positive implicit null input requiredness contradicts the actual Kotlin decoder #807, 🐛🧑‍💻 - Copilot review falsely treats Ktor Application.routing as a detached subtree despite resolved implementation and passing export #809.
• Large comparisons and diagnostics: support complete bounded comparison assessment after file-recovery exhaustion and expose invalid completed progress results through actionable diagnostics. References: 🐛🧑‍💻 - Support complete large comparison assessment after file recovery budget exhaustion in #773, 🐛🧑‍💻 - Expose completed progress assessment validation failures instead of opaque agent.failed #774.
• Native verification: keep JVM/Gradle account configuration inside private verification profiles and propagate the supported library path needed by native Python toolcache interpreters. References: 🐛🧑‍💻 - Private verification HOME does not redirect JVMGradle account level configuration #775, 🐛🧑‍💻 - Documented native Python setup cannot start Linux toolcache interpreter without supported library path propagation #776.
• Workflow lifecycle: retain canceled PR-link recovery identity, preserve closing references consistently across description/approval, and complete release issues only after publication and development reconciliation. References: 🐛🧑‍💻 - Cancelled PR linking loses original base and recovery marker after a newer invocation #785, 🐛🧑‍💻 - Release issue closes and reaches 100 at production promotion before publication and reconciliation #792, 🐛🧑‍💻 - PR description replacement drops closing reference while approval requires its text #803.
• Operator recovery: document complete paginated job inventory and reliable per-job log collection when advisory checks have no execution log, preserving real workflow failures and partial diagnostics. Reference: 🐛🧑‍💻 - Advisory checks become logless Actions jobs and break complete run log retrieval #817.

Quality evidence and measured exact-line-location limitations remain documented in quality/bugbot/evidence/. Deterministic/reference regression results are separate from actual model observations. This release does not establish consumer runtime adoption or resolve unrelated consumer business defects.

Additional Context

Release the verified development snapshot after the bug-fix batch is merged and a fresh union of open label:bug and native type:Bug issues is empty. Use the normal Action-managed release, production promotion, npm/GitHub publication and development reconciliation. Preserve required checks and exact-head review evidence.