v0.24.1

---

version: 0.24.1
date: 2026-06-10
headline: "Patch — dos_mcp becomes publishable to the official MCP Registry, and the bundled plugin validates clean."
themes: ["mcp", "skills", "distribution"]
highlights:

• "server.json + an OIDC publish workflow target the official MCP Registry"
• "PyPI README carries the registry's mcp-name ownership marker"
• "uvx one-liner: a dos-kernel console-script alias launches the MCP server"
• "Four plugin skills' YAML frontmatter fixed; claude plugin validate --strict green"
• "glama.json lets the owner claim the Glama directory listing"

---

TL;DR — The Tier A distribution release: everything dos_mcp needs to publish
to the official MCP Registry (which PulseMCP, Glama, and other aggregators
ingest), plus the frontmatter fix that makes the Claude Code plugin pass the
community-marketplace validation gate. No kernel behavior changes.

mcp — the MCP Registry publish surface

• server.json (repo root) — the registry manifest, schema 2025-12-11,
  named io.github.anthony-chaudhary/dos-kernel, pinning the dos-kernel
  PyPI package at this release's version.
  • Why: the official MCP Registry is the one publish that fans out — PulseMCP
    and Glama auto-ingest from it.
  • How: mcp-publisher validate green against the live registry schema.
• mcp-registry-publish.yml — a manual-dispatch GitHub Actions workflow that
  authenticates via OIDC (no stored token), validates, preflights (refuses on
  version skew or a not-yet-released / marker-less PyPI pin), publishes, and
  reads the record back out of the registry.
  • Why: the registry validates the PyPI README of the EXACT pinned version,
    so the publish must sequence after this release reaches PyPI.
• The mcp-name ownership marker — the README (assembled from
  docs/readme/95_citation-license.md) now ends with the registry's PyPI
  ownership token as a reader-invisible HTML comment.
• A dos-kernel console-script alias — the same dos_mcp.server:main
  entrypoint under the dist's own name, so uvx --from "dos-kernel[mcp]" dos-kernel (the registry's launch composition) and uvx "dos-kernel[mcp]"
  are real commands. Without the [mcp] extra it fails loudly with the same
  install hint as dos-mcp. The umbrella CLI stays dos.
• glama.json — Glama's maintainer-claim manifest at the repo root.

skills — the plugin passes the marketplace gate

• Four SKILL.md frontmatters YAML-quoted — dos-dispatch-loop,
  dos-self-improve (source pack) and dos-setup, dos-stats (authored in
  build_plugin.py) had unquoted description: scalars carrying a mid-line
  ": ", which YAML rejects; at runtime the metadata silently dropped.
  • Why: claude plugin validate — the exact gate the community-marketplace
    review pipeline runs — failed on them; it now passes --strict.
  • How: quoted scalars at the source; plugin copy regenerated by
    scripts/build_plugin.py.

Also in this tag

• The repo grew the GitHub topics + directory metadata for MCP discovery
  (no code change).