Context
The OpenSSF Silver documentation and previous-version criteria require a current roadmap and a clear maintenance or update policy. Release automation exists, but supported versions, end-of-life expectations, and roadmap status are not published as a durable contract.
Follow-up to #22.
Acceptance criteria
- Publish a version-support policy covering security fixes, prereleases, and end-of-life handling.
- Publish a concise roadmap that distinguishes committed work from exploratory work.
- Define how documentation is kept current when releases or trust-boundary contracts change.
- Link release achievements without overstating future availability.
- Update the corresponding OpenSSF Silver answers with public evidence links.
Context
The OpenSSF Silver documentation and previous-version criteria require a current roadmap and a clear maintenance or update policy. Release automation exists, but supported versions, end-of-life expectations, and roadmap status are not published as a durable contract.
Follow-up to #22.
Acceptance criteria