You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
scripts/collections/README.md was updated in commit 18ce4c6 (PR #1834 — feat(agents): add Vally evaluation agents and prompts), but the description of Modules/CollectionHelpers.psm1 remains stale. The README still reads:
Modules/CollectionHelpers.psm1 — YAML parsing, frontmatter, and collection helpers
This no longer accurately describes the module. PR #1834 added strict-safe maturity propagation logic that introduced three new exported functions:
Function
Description
Get-CollectionMaturityVocabulary
Returns the ordered, canonical list of accepted maturity values (single source of truth for the maturity vocabulary)
Get-CollectionMaturityRank
Returns the maturity precedence map used for aggregation propagation; strictest maturity wins
Resolve-StrictSafeMaturity
Resolves a maturity to a rankable value, defaulting to experimental when an unrecognized value is encountered (strict-safe fallback prevents invalid maturity from silently shipping as stable)
These three functions are exported by the module and consumed by Validate-Collections.ps1 during collection aggregation.
Expected Behavior
scripts/collections/README.md should:
Update the Modules/CollectionHelpers.psm1 description to reflect the new capabilities:
Optionally add a brief explanation of the strict-safe maturity propagation behavior so contributors understand why an unrecognized maturity value defaults to experimental rather than failing.
The strict-safe maturity propagation ensures that an invalid maturity value in a source collection cannot silently produce a stable artifact in the generated plugin output — it defaults to experimental instead.
docs/customization/collections.md documents the user-facing maturity field in collection manifests but does not describe the internal validation and propagation behavior in CollectionHelpers.psm1.
Component
Documentation
Bug Description
scripts/collections/README.mdwas updated in commit18ce4c6(PR #1834 — feat(agents): add Vally evaluation agents and prompts), but the description ofModules/CollectionHelpers.psm1remains stale. The README still reads:This no longer accurately describes the module. PR #1834 added strict-safe maturity propagation logic that introduced three new exported functions:
Get-CollectionMaturityVocabularyGet-CollectionMaturityRankResolve-StrictSafeMaturityexperimentalwhen an unrecognized value is encountered (strict-safe fallback prevents invalid maturity from silently shipping as stable)These three functions are exported by the module and consumed by
Validate-Collections.ps1during collection aggregation.Expected Behavior
scripts/collections/README.mdshould:Modules/CollectionHelpers.psm1description to reflect the new capabilities:experimentalrather than failing.Steps to Reproduce
scripts/collections/README.md.Modules/CollectionHelpers.psm1.scripts/collections/Modules/CollectionHelpers.psm1and search forGet-CollectionMaturityVocabulary— the three new exported functions are present but undocumented in the README.Additional Context
18ce4c6(PR feat(agents): add Vally evaluation agents and prompts #1834).maturityvalue in a source collection cannot silently produce a stable artifact in the generated plugin output — it defaults toexperimentalinstead.docs/customization/collections.mddocuments the user-facingmaturityfield in collection manifests but does not describe the internal validation and propagation behavior inCollectionHelpers.psm1.