[GuillaumeRx]

Explanation

The package can validate one Changeset file, but consumers still have to find and read every Changeset themselves. This PR adds repository-level orchestration:

lintChangesets
  discover direct .changeset/*.md files
  read each file in deterministic order
  validateChangesetFile
  return structured diagnostics

lintChangesets validates every pending Changeset in a repository. It skips README.md, non-Markdown files, and nested directories. It fails clearly if .changeset/ or a Changeset file cannot be read.

This PR adds only the library API. The CLI and CI integration remain separate.

References

• Follows feat: validate changeset files #93

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

[cryptodev-2s]

One minor nit otherwise looks good to me8

[cryptodev-2s]

Nit: nit do we want to Mirror https://github.com/changesets/changesets/blob/main/packages/read/src/index.ts#L9 at least AGENTS.md I believe we would want to leave instructions here on how agents can write changesets ?

[GuillaumeRx]

We can add it late if it's really a problem but I would expect us to store this outside of this folder