ict-engine-release-mirror-ci

name	ict-engine-release-mirror-ci
description	Use when publishing ict-engine to the private release mirror, when GitHub Actions fails after publication, when a published tag needs correction, or when source repo and release mirror targets may be confused.

ICT Engine Release Mirror CI

Core rule

Publishing is part of verification. Local gates prove the export is worth publishing; the release mirror and its remote GitHub Actions prove cross-OS consumer safety. Do not stop at local green when the user's concern is whether another operating system will fail.

For ict-engine, the outward release target is Undermybelt/ict-engine-release. The source repo Undermybelt/givenup-ict-engine is provenance and development history, not the release surface.

Use when

• User says release, publish, 发布, 发版, mirror, ict-engine-release, GitHub Actions failed after publish, run failed, cross-OS CI, correction release.
• A tag already exists and the remote release or CI is wrong.
• Local source checks pass but the release mirror may differ.
• Dirty shared checkout makes packaging or docs/runtime gates unreliable.

Release loop

1. Re-read repo-local instructions and live handoff/TODO surfaces before touching files.
2. Protect the shared checkout: git status --short, stage exact files only, never git add . from a dirty ict-engine tree.
3. Build a clean committed export or clean mirror clone. Validate from that clean tree, not from a dirty working tree.
4. Run CI-equivalent local gates before publishing:
   • python3 support/scripts/ci/check_docs_runtime_isolation.py
   • release privacy audit with compact output and release_blocking_hits=0
   • cargo fmt --check