chore: sync the v1.1.6 promotion merge into development

[mohanagy]

Pull request

Summary

Refs #453. Brings the v1.1.6 promotion merge (d5a932d, PR #455) into development's ancestry so the two long-lived branches do not drift.

Each release promotion lands a merge commit on main that development never receives. Left unsynced, the next promotion pull request reports BEHIND and surfaces a phantom textual conflict that is not real.

Content is unchanged. git diff <development-head-before> HEAD --stat is empty — this is an ancestry fix only, no file differs.

Merge with a merge commit. Do not squash. Squashing here defeats the entire purpose: it would create a new SHA that main never receives and reintroduce the drift this pull request exists to remove.

Verify afterwards with git merge-base --is-ancestor origin/main origin/development.

Security impact

None. No file content changes; this only records main's promotion merge in development's history.

Validation

• A failing test was observed first for each behavior or configuration-contract change — not applicable, no content change.
• git diff between the previous development head and this branch is empty.
• The published v1.1.6 artifact is unaffected; this does not alter any released commit.

🤖 Generated with Claude Code