Manual Cloudron deploy and ship-gate workflow

Cloudron deploy is operator-triggered only. Cursor agents follow a ship-gate: ask after CI, ask to deploy after merge, verify Change Log hubs, then ask whether to create a GitHub Release.

Changes

• Stop auto-deploy on green main; Deploy MyAPES Core to Cloudron runs only on workflow_dispatch.
• Add ship-gate agent rule and skill with next-actions menus for merge, deploy, changelog hubs, and GitHub Release.
• Document that the app Change Log Hub updates from releases.json on the same Cloudron deploy, and that sibling website changelogs need an explicit operator ask.

Affected areas

• Cloudron deployment workflow
• Agent ship-gate documentation
• Public Change Log Hub (via deploy)

Version rationale

Patch release: changes how operators and agents trigger deploy and release without changing application product features for end users.

References

• Issue #167
• Pull request #168

MyAPES Core 0.31.3 (2026-08-29) · stable · patch