chore: update agents to the current toolbox release

[evergine-bindings-automation]

Brings the installed agentic workflows back in step with the current
v1 of EvergineTeam/Evergine.Bindings
and the current gh-aw compiler.

	Installed	Current
Toolbox	ace4e8d477b877e973e5c748a81aff8f24c6fe42	4c15efde1d1789d14befc9e2b5ca711a0aba1c4c
Compiler	v0.85.4	v0.88.2
Agents	binding-updater ci-doctor cpp-wrapper-porter	binding-updater ci-doctor

What drifted: toolbox+compiler+agents. A row whose two
columns match did not move and is shown so the others can be read
against it. The agents column is decided by binding.yml:
cpp-wrapper-porter belongs where there is a wrapper: block,
binding-updater where there is a generator:, and ci-doctor
everywhere.

Neither moving the toolbox tag nor gh-aw cutting a release updates
anything on its own — a repository keeps the commit and the compiler it
was built against until something recompiles it, and nothing fails in
the meantime. That is what makes the drift easy to accumulate and
invisible without looking, and it is why compiler drift is checked at
all: the fleet sat on gh-aw v0.85.4 for three weeks past a fix it
needed, while this job reported everything current.

Review the diff as you would any workflow change: the compiled
.lock.yml files are generated, but the .md frontmatter is not.

[github-actions]

API gate: additive

Every symbol that existed still exists, unchanged. Nothing that compiled before stops compiling.

Target framework	Added	Removed
net10.0	+0	-0

_{Enum and constant values are part of the measured surface: a renumbering keeps compiling and sends the wrong number to the driver, so it counts as a removal.}