OPENAI_PLUGIN.md line 5 states, in the present tense, that the plugin is published at version 3.29.0, approved 2026-09-04. submission/submission-pack.json correctly freezes 3.29.0 as the version that was submitted. But submission/listing.json and .codex-plugin/plugin.json are already at 3.34.0, five releases later, and no SSOT manifest tracks the line in OPENAI_PLUGIN.md.
A reader cannot tell whether 3.29.0 is what the directory serves today or a historical note, and the sentence sits directly under prose describing the current seven-skill architecture with no date scoping.
Maintainer decision
Either resubmit and update the version and date, or reword the line to mark it as the last approved submission and say that later versions are pending or unsubmitted. If the line is meant to track the live listing, register it in .ssot-local.yaml so it is checked.
Filed as a question rather than help wanted because resolving it requires checking the live OpenAI directory listing, which only the maintainer can do.
OPENAI_PLUGIN.mdline 5 states, in the present tense, that the plugin is published at version 3.29.0, approved 2026-09-04.submission/submission-pack.jsoncorrectly freezes 3.29.0 as the version that was submitted. Butsubmission/listing.jsonand.codex-plugin/plugin.jsonare already at 3.34.0, five releases later, and no SSOT manifest tracks the line inOPENAI_PLUGIN.md.A reader cannot tell whether 3.29.0 is what the directory serves today or a historical note, and the sentence sits directly under prose describing the current seven-skill architecture with no date scoping.
Maintainer decision
Either resubmit and update the version and date, or reword the line to mark it as the last approved submission and say that later versions are pending or unsubmitted. If the line is meant to track the live listing, register it in
.ssot-local.yamlso it is checked.Filed as a question rather than help wanted because resolving it requires checking the live OpenAI directory listing, which only the maintainer can do.