fix: remove truncated (e.g.) example from hash-type schema description

[Copilot]

The hash-type field in the generated JSON schema produced a truncated description: "Hash algorithm used for the hash value (e.g.".

The jsonschema struct tag uses commas as key=value separators. The description (e.g., SHA256, SHA512) contained commas, causing the parser to treat SHA256 and SHA512) as separate invalid entries and truncating the description at the first inner comma.

Changes

• internal/projectconfig/component.go: Removed (e.g., SHA256, SHA512) from the HashType field's jsonschema description — the valid values are already expressed via enum=SHA256,enum=SHA512 in the same tag.
• scenario/__snapshots__/TestSnapshots_config_generate-schema_stdout_1.snap: Updated snapshot to reflect the corrected description.
• scenario/__snapshots__/TestSnapshotsContainer_config_generate-schema_stdout_1.snap: Updated snapshot to reflect the corrected description.

Before:

jsonschema:"...,description=Hash algorithm used for the hash value (e.g., SHA256, SHA512)"
// Generated: "description": "Hash algorithm used for the hash value (e.g."

After:

jsonschema:"...,description=Hash algorithm used for the hash value"
// Generated: "description": "Hash algorithm used for the hash value"

[Copilot]

Pull request overview

Fixes a truncated JSON schema description for the hash-type field by removing comma-containing example text from the jsonschema struct tag (since the tag parser treats commas as option separators). This improves the generated schema output for TOML config validation without changing the actual allowed values (still enforced via enum).

Changes:

• Remove the (e.g., SHA256, SHA512) example from the HashType field’s jsonschema description to avoid truncation.
• Rely on the existing enum=SHA256,enum=SHA512 entries in the same tag to convey valid values.

[dmcilvaney]

@copilot Update the scenarios, and ensure they work after.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• example.com
  • Triggering command: /tmp/go-build103337162/b649/sourceproviders.test /tmp/go-build103337162/b649/sourceproviders.test -test.testlogfile=/tmp/go-build103337162/b649/testlog.txt -test.paniconexit0 -test.timeout=10m0s /tmp/go-build103337162/b580/vet.cfg ternal/app/azlde-errorsas ternal/app/azlde-ifaceassert ux-amd64/pkg/tool/linux_amd64/vet --gdwarf-5 --64 ter-statement ux-amd64/pkg/too-buildtags o_.o�� .4.11/ratelimite-errorsas .4.11/ratelimite-ifaceassert ux-amd64/pkg/tool/linux_amd64/vet -pthread nal/utils/qemu -fmessage-length/tmp/go-build103337162/b606/_pkg_.a ux-amd64/pkg/too-trimpath (dns block)
• invalid-domain.there.is.no.such.resource
  • Triggering command: /tmp/go-build103337162/b642/rpmprovider.test /tmp/go-build103337162/b642/rpmprovider.test -test.testlogfile=/tmp/go-build103337162/b642/testlog.txt -test.paniconexit0 -test.timeout=10m0s go1.25.6 -c=4 -nolocalimports -importcfg /tmp/go-build103337162/b573/importcfg -pack /home/REDACTED/go/pkg/mod/github.com/thejerf/slogassert@v0.3.4/assertions.go _vi4MaLkzvcg -qui�� hellquote@v0.0.0-errorsas hellquote@v0.0.0-ifaceassert ux-amd64/pkg/tool/linux_amd64/vet 337162/b114/ nal/utils/cloudi-atomic ead ux-amd64/pkg/too-buildtags (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)