fix: resolve catalog validation errors and eslint issues #13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes catalog validation errors discovered by automated tests and resolves pre-existing eslint issues.
Issues Found
The new Jest validation suite (1158 tests) discovered:
security-privacyinstead ofsecurityscript-utils.jsChanges
Catalog fixes:
security-privacy/tosecurity/directorysecurity-privacydirectoryLint fixes:
script-utils.jsSelectionContext.jsx: lazy initialization instead of setState in useEffectThemeContext.jsx: proper context export patternTesting
Validation Coverage
Tests validate: software/config schemas, category enums, license enums, unique kebab-case IDs, winget ID format, hex colors, non-empty command arrays.
This PR demonstrates the new CI pipeline catching real issues before merge.