golem-add-initial-files

To provision initial files into a Golem agent filesystem, you add `agents.<AgentType>.files` entries in your `golem.yaml` manifest, specifying `sourcePath`, absolute `targetPath`, and `permissions` to ensure configuration and assets are available at agent startup.

Initial file system provisioning is the process of automatically adding required configuration and supporting files into a Golem agent's virtual filesystem based on manifest definitions, ensuring the right files exist when the agent starts.

You can use remote HTTP and HTTPS sources to add initial files to your Golem agent. The provisioning process supports remote single-file downloads alongside local files and local directories, applying them to the agent's virtual filesystem.

File inheritance and merge modes work by defining files at component template, component, agent type, and preset levels, then combining them using `append`, `prepend`, or `replace` merge rules to finalize the agent's initial file set.

The main constraint when adding initial files is that all resolved target paths must be unique. Additionally, the `targetPath` must be an absolute path inside the agent filesystem, while file permissions default to `read-only` unless explicitly set to `read-write`.