Skip to content

docs: state conformance plainly rather than as a version milestone - #7

Merged
jpantsjoha merged 1 commit into
mainfrom
docs/conformance-wording
Aug 7, 2026
Merged

docs: state conformance plainly rather than as a version milestone#7
jpantsjoha merged 1 commit into
mainfrom
docs/conformance-wording

Conversation

@jpantsjoha

Copy link
Copy Markdown
Owner

"As of v0.2.0 this plugin conforms to…" implies it did not previously. For a reader deciding whether to install, the fact that matters is the present one — so the README now simply cites Compliant with Agent Plugins 1.0.0.

Same correction applied to the standards note in docs/SUBMISSIONS.md, which carried identical phrasing. CHANGELOG.md keeps its dated framing — that is what a changelog is for.

Docs only. No change to what is claimed, only how it reads.

"As of v0.2.0 this plugin conforms to..." reads as an admission that it did not
before. For a reader deciding whether to install, the relevant fact is the
present one: it is compliant with the standard. Version history belongs in the
changelog, which keeps its dated framing.

Applies the same correction to the standards note in docs/SUBMISSIONS.md, which
carried the identical phrasing.
@jpantsjoha
jpantsjoha merged commit 23a20c2 into main Aug 7, 2026
1 check passed
@jpantsjoha
jpantsjoha deleted the docs/conformance-wording branch August 7, 2026 11:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants