chore(release): 0.1.32

[github-actions]

Summary

Keep a release proposal current with changes merged into main.

Changes

Update the package version and draft release notes. The version header and PR title are maintained by automation. Edit the marked note sections in .github/release-notes.md; edited or deleted sections become human-owned. New suggestions appear in subsequent bot comments. The PR description is never regenerated.

Testing

The updater does not run package tests. Check required CI and Codex review on the current head before merging. Request a final Codex review if the last review targets an older head. Record any additional checks here.

Risk and rollout

Merging this PR starts the existing CI and protected release process. Review migration details and complete the public disclosure review before merging.

Public disclosure review

• No customer, partner, prospect, or user identities, data, or identifying details are included.
• No credentials, personal data, private source, scan findings, or nonpublic links or tickets are included.
• I reviewed the branch name, title, description, commits, changes, comments, logs, screenshots, attachments, and links for public disclosure.

[github-actions]

Release proposal updated through main commit aa2f40bebf7e57ed98c1d09e43b5ffc413a3d41e.

The note sections still match the generated draft and were refreshed.

These suggestions use merged titles, not a review of migration requirements. The committed notes remain authoritative.

Highlights

• return the Deep Scan ID in structured output (#1026)

Upgrade notes

Review compatibility and document any required migration steps before releasing.

@codex review the current head a1f3a98.

[chatgpt-codex-connector]

Note

To use Codex here, create a Codex account and connect to github.