Add enum metadata to hook params

[ChiragAgg5k]

Summary

• add optional enum metadata to Hook::param()
• store enum metadata with hook params for downstream route/platform usage
• add unit coverage for enum metadata

Tests

• vendor/bin/phpunit
• php -d error_reporting=22527 vendor/bin/pint --test src/Servers/Hook.php tests/Servers/Unit/HookTest.php

[greptile-apps]

Greptile Summary

This PR adds an optional ?object $enum = null parameter to Hook::param() to carry enum metadata (e.g., name and value map) for downstream route/platform usage.

• Hook::param() gains a last, nullable $enum parameter that is stored in the params array alongside existing metadata fields — fully backward-compatible since it defaults to null and is appended last.
• A new unit test verifies that a stdClass-based enum object is stored and returned unchanged via getParams().

Confidence Score: 5/5

A small, additive change with no logic alterations and a matching unit test — safe to merge.

The new $enum parameter is appended last with a null default, so all existing callers remain unaffected. The value is stored verbatim in the params array without any processing, keeping the change entirely non-breaking. The unit test confirms round-trip storage and retrieval.

No files require special attention.

Important Files Changed

Filename	Overview
src/Servers/Hook.php	Adds optional ?object $enum = null as the last parameter of param() and stores it in the params array — backward-compatible, no logic changes.
tests/Servers/Unit/HookTest.php	Adds testParamEnumCanBeSet using a stdClass object to verify the enum metadata is stored and retrievable via getParams().

_{Reviews (1): Last reviewed commit: "Add enum metadata to hook params" | Re-trigger Greptile}