I'm trying to use the php config structure to configure workflows in my application.

The docs of the workflow component lack any information to even indicate that metadata is supported on workflows, places and transitions. But the config will actually build the methods on said configs.

Using the following config

// config/packages/workflow.php
use Symfony\Config\FrameworkConfig;

return static function (FrameworkConfig $framework): void {
    $workflows = $frameworkConfig->workflows();
   
    $workflow = $workflows->workflows('workflow_name');
    // Configure other workflow information

    $workflow->place()
        ->name('some_place_name')
        ->metadata(
            [
                'place_specific_metadata_key' => 'value'
            ]
        );
};

I get the an error from PHPStan among the lines of:

 Parameter #1 $value of method Symfony\Config\Framework\Workflows\WorkflowsConfig\PlaceConfig::metadata() expects list|Symfony\Component\Config\Loader\ParamConfigurator, non-empty-array<string, mixed> given.

Looking at the generated PlaceConfig in the cache i noticed the following param on the metadata method:

     * @param ParamConfigurator|list<ParamConfigurator|mixed> $value

This seems to be a bit of a weird behavior, allowing to store metadata, but not actually getting the option to set keys for the metadata you are trying to add. Especially as the GetMetadataTrait Seems to expect the key of the set metadata to be a string.

The Configuration from the workflow component defines the metadata as an arrayNode, but even purposefully does not normalize the keys. (Giving the indication they want the defined keys to stay as they are in the configs)
Allowing you to create metadata configs with key: value using the yaml configs. As defining a yaml config with key value does not result in any errors.

Is this behavior on purpose?
Or is this a case where the ConfigBuilderGenerator just (incorrectly) assumes the node should be a list?