[mblua]

Release 0.44.0 publishes the changes merged since v0.43.0 through the existing GitHub Actions workflow to GitHub and npm next. npm latest remains 0.43.0 pending a separate promotion.

Includes the eight exact V1 evidence files generated twice against live Git/GitHub/npm facts, synchronized version surfaces, release notes and the refreshed packaged npm README. Scope covers task CLI/IPC and terminal/sidebar status, project/team skills, Antigravity suggestions, nested memory archives, empty task descriptions and Windows long-path fixes. Notes retain incomplete physical UI verification and simulated reparse fixture limitations.

Validation: live candidate checks passed, SHA256SUMS verified, all eight staged evidence blobs match the generator bytes, version synchronization passed. Diff check passes for edited files; generated release-plan.md retains four intentional Markdown hard-break lines with two trailing spaces, required to preserve exact evidence bytes. Package dry-run and pack passed from npm/, including the nine expected wrapper files. Full regression CI is requested with ci:full; no tag or publication occurs until it passes and the final merged commit is verified.

Closes #2944.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[mblua]

Main delta reviewed: e48382f -> d829022, merged #2942 adds independent identity/schema2 contracts and tests in settings.rs and coding_agents_catalog.rs. Existing readers/persistence remain unchanged; no overlap with this PR's release/version/npm/changelog paths or publishing inputs.

GitHub's live main rules require strict_required_status_checks_policy=true. Updated the branch through the supported GitHub merge operation to satisfy that actual rule; full CI must validate the resulting head. All eight V1 evidence blobs remain byte-identical to the live-generated bundle and version:check passes. The deployed release guard binds the recorded planning snapshot but does not require that snapshot equal latest main; no changed release-input fact requires regeneration. The final merged commit and actual assets will be reverified before tagging.