[wisdommen]

Summary

Prepares UltiBackup 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 section becomes ## [2.0.0] - 2026-10-21. It adds one entry (in English and Chinese) stating the release requires UltiTools-API 6.3.0 and raises the module's UltiTools API level from 620 (declared by the released 1.0.0) to 630, so operators upgrade the framework before replacing the module JAR. The existing api-version entry now names 620 as the released 1.0.0 value, and its README sentence matches the README at this head (framework minimum only).
.github/workflows/publish.yml	Deleted. On every push to master it built with tests skipped, 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. maven-ci.yml (build and tests) is unchanged and is the only workflow left.

The first commit on this branch (6e86d3f) added a publishing wrapper and its tests; the second commit (aa09fb0) removes both and adopts the separate manual publication path described above, so neither appears in the net diff.

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 aa09fb0: BUILD SUCCESS, 529 tests, 0 failures, 0 errors, 0 skipped.
• Net diff against master is exactly .github/workflows/publish.yml (deleted), CHANGELOG.md and pom.xml; no remaining workflow references a catalogue token, the catalogue CLI or gh release.
• The built JAR's plugin.yml declares name UltiBackup, version 2.0.0, api-version: 630 and identify-string: ultibackup.
• A real-server acceptance run of every UAT-CHECKLIST.md row on the JAR built at this head is part of the merge gate.

Issue closure

None

🤖 Generated with Claude Code

[wisdommen]

Gate summary for head aa09fb0

• Own code review: two runs (gpt-6.1-sol, high effort): the full diff, then a confirmation run on the fix commit. No open P1 or P2.
• Cross-family code review: two runs by a Claude Opus reviewer. No open P1 or P2. Remaining P3 notes are tracked in Follow-up from #38: backup browser refresh with no backups, and housekeeping (2.0.1) #39.
• Build and tests: clean mvn -B clean verify at this head: 529 tests, 0 failures; the coverage gate passes. The JAR built from this head declares version 2.0.0, api-version: 630 and identity ultibackup.
• Real-server acceptance: every one of the 40 UAT-CHECKLIST.md rows passed on a dedicated Paper server running the released UltiTools-API 6.3.0, against the exact JAR built at this head (SHA-256 1fcc15199b493c20292a88b7181d100db843aa76855b2a40e1b32f01672475eb, checked at start and end). The two GUI rows were checked with a real Java client.
• CI: the Maven CI check is green at this head.
• Codacy: not configured for this repository (N/A).

One pre-existing defect surfaced during acceptance, outside every checklist row: the backup browser does not refresh after it was opened with no backups (present since 1.0.0; the data is saved, and reopening the browser shows it). It ships as a known issue in 2.0.0 and is scheduled for 2.0.1 in #39.

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

🤖 Generated with Claude Code