Set Json's repository topics and SubscribeTo property #38

Context and request

The repository's GitHub metadata is incomplete against Required repository metadata.

Current state: the description is A PowerShell module for typical Json related tasks., the default branch is main, the licence is MIT, and the Type custom property is correctly set to Module. Missing: the repository has no topics, and the SubscribeTo custom property is unset, so the repository is opted out of managed-file distribution entirely.

Acceptance criteria.

• The repository has topics that help users find it.
• SubscribeTo is set to the file types the distribution runtime should own here, or a deliberate decision to leave it unset is recorded in this issue with the reason.
• Type remains Module and the repository still appears under gh search repos --owner PSModule 'props.Type:Module'.
• The description still reads as a user-facing summary of what the module does.

Technical decisions

This produces no repository artifact, so it follows the operational delivery path: the action, expected evidence, and verifier are named before work starts, and completion requires an audit comment with captured output.

The SubscribeTo decision is not automatic. Selecting a file type hands ownership of that file to the distribution runtime, so any repository-local customization is overwritten. The files this repository has customized versus adopted verbatim should be established first — the managed-file realignment work covers exactly that ground, so this should follow it.

Topics are chosen for discoverability on the PowerShell Gallery and GitHub search, not as keyword stuffing.

The description is left as-is. It already starts with A PowerShell module, is user-facing, and avoids implementation detail.

Evidence required for closure: the output of gh api /repos/PSModule/Json/properties/values and gh repo view PSModule/Json --json repositoryTopics, posted as an audit comment, plus an independent check against each acceptance criterion.

Implementation plan

• Agree the topic list
• Establish which managed files this repository has customized, to inform the SubscribeTo selection
• Decide the SubscribeTo value, or record the decision to leave it unset and why
• Apply topics and the custom property
• Capture gh api /repos/PSModule/Json/properties/values and gh repo view PSModule/Json --json repositoryTopics output
• Post the audit comment with the captured evidence and the verification result for each criterion