Ops Post Transfer Verification

---

title: Post-Transfer Verification description: End-to-end checklist after moving repository and release ownership

Post-Transfer Verification

Run this after GitHub transfer, npm Trusted Publishing setup, OpenUPM metadata updates, and Unity Asset Store account checks.

Repository

1. Clone from git@github.com:Ambiguous-Interactive/DxMessaging.git or the HTTPS equivalent.
2. Run git fetch --all --tags --prune.
3. Confirm default branch, tags, release drafts, and protected branches.
4. Confirm maintainers can open and review pull requests.
5. Confirm stale links are gone:

npm run validate:repo-identity

Validation

Run from a clean tracked state:

npm run test:scripts
npm run test:unity-contracts
npm run validate:npm-meta
npm run validate:llms-txt
npm run validate:all
node scripts/validate-workflows.js

If validate:untracked-policy fails, either commit intended files or add a documented ignore rule. Do not ignore files that should be part of the release change.

CI

1. Trigger Unity Tests manually for one Unity version and one mode (the standalone mode covers IL2CPP via the native game-ci testMode: standalone player build).
2. Trigger Unity Benchmarks only when runner capacity is available.
3. Open a same-repository pull request and confirm licensed Unity checks run.
4. Open or simulate a fork pull request and confirm licensed Unity checks skip.
5. Confirm GitHub-hosted checks still run for fork PRs.

Release Dry Run

There is no release dry-run workflow. Use local validation before tagging:

npm run validate:npm-meta
npm pack --json --dry-run --ignore-scripts

Do not push a real vX.Y.Z tag until npm Trusted Publishing, runner access, GitHub Release permissions, and OpenUPM metadata are all verified.

Public Distribution

After the first Ambiguous release:

1. GitHub Release contains .tgz and .sha256 assets.
2. npm page shows the new version and provenance.
3. OpenUPM page shows the new version.
4. Git URL install works from a clean Unity project.
5. npm scoped registry install works from a clean Unity project.
6. Documentation site resolves at https://ambiguous-interactive.github.io/DxMessaging/.
7. README badges point at Ambiguous-Interactive/DxMessaging.
8. Unity Asset Store public listing URL is recorded locally, if applicable.

Local Runbook Closeout

In .operator-runbooks/ambiguous-release-setup.md, record only:

• public URLs
• public PR or issue links
• dates when public verification was completed
• non-sensitive next actions

Do not record secrets, account screenshots, publisher identifiers, recovery codes, private reviewer messages, or private account metadata.