Release 0.12.2: the operator's tool descriptions, and the registry marker

[arpanghoshal]

Cuts 0.12.2 so that two things on main reach the people who would use them, and so
that the MCP registry listing can publish itself.

The operator's tool descriptions are behaviour, not documentation. #220 gave every
tool and every argument a description: that control filters rather than selects, that
since takes 24h as readily as a timestamp, that a failed resolution is what
unblocks a retry, that list_pending_approvals is where the request ids come from.
That text is what an MCP client puts in front of a model. It has been on main since
0.12.1 was tagged, which means no installed copy has it.

The mcp-name: marker only works from a published release. The registry verifies
the namespace by reading it out of the long description of a distribution on PyPI, and
0.12.1 was uploaded before the marker existed. Checked again on this branch: PyPI's
0.12.1 description has no marker, and the registry answers 404 for
io.github.CTRLRun/ctrlrun-mcp-operator.

Tagging this is what publishes the listing. The registry job added in #222 runs after
the PyPI upload, authenticates with an OIDC token, and needs nobody at a terminal.

What is in it

Everything merged since 0.12.1: #217, #218 and #222 (the manifest, its pins, the publish
job), #219 (glama.json), #220 (the tool descriptions), #221 (the README's MCP row
pointing an approver at their own page). No change to the enforcement path.

The version-carrying files

All four move together, which the suite enforces: pyproject.toml, CHANGELOG.md,
CITATION.cff, and both of server.json's version fields.

mcp-publisher validate passes against the live registry at 0.12.2:

Validating against https://registry.modelcontextprotocol.io...
✅ server.json is valid

Full suite green locally, 4228 passed and 366 skipped.

Not in this PR

adapters/PUBLISHED.toml is stale for the fourth release running: it records 1.2.0 /
<0.12 while PyPI has served 1.3.0 / <0.13 since 2026-09-15. It blocks nothing here,
because the published adapters already allow a 0.12.x kernel, and it is its own fix
rather than something to bury in a release PR.

Summary by CodeRabbit

• Documentation

  • Added release notes covering operator tool and argument descriptions, improved guidance for read tools, official MCP Registry publication, and Glama metadata.
  • Corrected the MCP link in the README.

• Chores

  • Updated project, package, server, and citation metadata to version 0.12.2.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: f26cc435-d96e-44df-a3fd-fb4c13a03764

📥 Commits

Reviewing files that changed from the base of the PR and between 42d0d24 and 63244fb.

📒 Files selected for processing (4)

• CHANGELOG.md
• CITATION.cff
• pyproject.toml
• server.json

Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review.

---

📝 Walkthrough

Walkthrough

The pull request adds the 0.12.2 changelog entry and updates the project, citation, and server metadata versions from 0.12.1 to 0.12.2.

Changes

Release metadata

Layer / File(s)	Summary
Release documentation CHANGELOG.md	Adds the 0.12.2 release entry and documents operator descriptions, MCP registry publication details, Glama metadata, and the README MCP-link correction.
Version metadata pyproject.toml, CITATION.cff, server.json	Updates the project, citation, server, and PyPI package versions to 0.12.2.

Priority: ➖ Normal

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 63244

The release metadata is consistent, and no actionable issue remains identified for this change.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the 0.12.2 release and names two primary changes: operator tool descriptions and the registry marker.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release-0-12-2

---

_{Comment @coderabbitai help to get the list of available commands.}