[wisdommen]

Summary

Prepares UltiMenu 2.0.0 against the released UltiTools-API 6.3.0. Merging this pull request publishes nothing: no tag, no GitHub release and no UltiCloud catalogue version. Publication happens later as a separate, manual step from the exact JAR built and accepted at this head.

The net change against master is exactly three paths:

Path	Change
pom.xml	Project version 1.0.0 → 2.0.0; UltiTools-API dependency 6.3.0-SNAPSHOT → 6.3.0 (the release on Maven Central). Nothing else.
CHANGELOG.md	The Unreleased heading becomes ## [2.0.0] - 2026-10-21 and the section states, in English and Chinese, that the release requires UltiTools-API 6.3.0 or later and that the module's api-version rises from 620 (declared by the last released version) to 630. Existing entries are otherwise reworded or condensed so they describe the final state (9 lines added, 9 removed in total).
.github/workflows/publish.yml	Deleted. On every push to master it built, created a v<pom version> tag and release, and uploaded to the UltiCloud catalogue. With it removed, the merge commit carries no publishing workflow, so this version bump cannot publish anything.

No source, plugin.yml, README or other workflow changes. The CI workflows that build and test remain; none references a catalogue token, the catalogue CLI or gh release.

Threat model

This change defends against an ordinary merge or push to master publishing a release or catalogue version.

Verification

• mvn -B clean verify at head 7d960cc: BUILD SUCCESS, 277 tests, 0 failures, 0 errors, 0 skipped; coverage checks pass.
• Net diff against master is exactly .github/workflows/publish.yml (deleted), CHANGELOG.md and pom.xml; git diff --check is clean.
• The built JAR's plugin.yml declares name UltiTools-Menu, version 2.0.0, api-version: 630 and identify-string: ultimenu.
• Real-server acceptance is part of the merge gate: either a recorded carry-over of the earlier full UAT run (only when src/main and UAT-CHECKLIST.md are unchanged since it) or a full run on the JAR built at this head.

Issue closure

None

🤖 Generated with Claude Code

[wisdommen]

Gate summary for head 7d960cc

• Own code review: one run (gpt-6.1-sol, high effort) on the full diff. No open P1 or P2.
• Cross-family code review: one run by a Claude Opus reviewer. No open P1 or P2. Remaining P3 notes are tracked in Follow-up from #37: release-note upgrade order (2.0.1) #38.
• Build and tests: clean mvn -B clean verify at this head: 277 tests, 0 failures; the coverage gate passes. The JAR built from this head declares version 2.0.0 and api-version: 630.
• Real-server acceptance: all 32 UAT-CHECKLIST.md rows are covered by passing evidence for the JAR built at this head (SHA-256 09ad4ddb282e8929c49d50088b53a39fefe2bd073a6a768cc719943bfe2847be): 32 carried forward from earlier real-server passes (row text unchanged), 0 re-run.
• CI: the Maven CI check is green at this head.
• Codacy: not configured for this repository (N/A).

Merging publishes nothing: this pull request deletes the CI publishing workflow, and 2.0.0 is published separately.