chore: promote v1.0.40 to main

[LeXwDeX]

Why

The reviewed native-tool settlement fix and the other accepted dev changes need one formal v1.0.40 delivery to main. The release PR must have its own SpecGit record and current-head acceptance; inherited acceptance for an older feature PR is insufficient.

Scope

Promote the accepted dev snapshot at 711e7b5 through the dedicated chore/543-stable-release branch into main. Update v1.0.40 notes with the latest completed integration CI evidence. Preserve all runtime code from dev and all existing gates. The deferred #531 local database maintenance remains excluded.

Approach

Use the canonical SpecGit bootstrap and an independently reviewed release binding. Compare the release branch against the accepted dev snapshot, allowing only delivery metadata and release-note updates. Validate notes, pass the full main-targeted CI matrix and SpecGit Acceptance, and run specgit finish against this release PR and exact head before merge. After main merge, dispatch release-fork from main and verify the formal tag, release assets, checksums and Latest state.

Acceptance

• The accepted dev runtime tree reaches the release branch unchanged.
• Release notes use the mechanically resolved 1.0.40 version and completed CI evidence, and pass the release renderer.
• Independent Standards/Spec review reports no unresolved findings.
• Typecheck including lint/DAG core, Linux full unit tests, generated client/SDK checks, all HttpAPI modes, Linux/Windows E2E and SpecGit Acceptance pass for the release PR.
• specgit finish returns exit 0 for PR chore(release): promote v1.0.40 to main #544 and its current head before merging to main.
• The authorized post-merge release is verified and its final links and commit recorded in the delivery report.

[LeXwDeX]

SpecGit delivery branch: chore/543-stable-release (draft pull request #544).