fix(react-kratos): recover existing npm release

[TorinAsakura]

Task

• Refs [Package] Kratos React для self-hosted Kratos #159
• Refs feat(react-kratos): upgrade Kratos client #160
• The merge-triggered release workflow created @atls/react-kratos@0.1.0 as a GitHub Release and committed the version change, but npm rejected the direct publish. At recovery start, the public registry still served 0.0.2.
• Add a bounded manual recovery path for the already-versioned 0.1.0 package. It checks out the exact version commit, verifies the manifest and that the version is absent from npm, then uses the existing Yarn workspace publisher and the org NPM_TOKEN. It does not create another version, tag, or GitHub Release and does not publish other workspaces.

How to verify

Before fix

1. Context: master at version commit 9bc23729472414c56d1a0a2d67f423dec0f05cfc after the failed publish run. Action: inspect Raijin workspace selection with and without the original GitHub PR event. Expected result: a local invocation without event context selects no workspaces; CI with the original PR event can select the changed packages again and defer another version bump. The recovery job therefore publishes the pinned existing version directly.

After fix

1. Context: this workflow change is merged and the org NPM_TOKEN has direct publish permission. Action: dispatch Publish to registry manually. Expected result: the recovery job checks out 9bc2372, verifies package version 0.1.0 and registry absence, installs immutably, then publishes only @atls/react-kratos@0.1.0. Confirm the registry version, packed exports, and consumer installation from npm rather than inferring success from the workflow exit code.
2. Context: 0.1.0 is already available from npm. Action: dispatch the same recovery job again. Expected result: the registry guard fails before the publish step; no new version or tag is created.

Proofs

• Failed automatic release: https://github.com/atls/reactjs/actions/runs/36614597758 — the changelog command was invalid, and npm returned 403 E_STAGE_REQUIRED at the first changed workspace. This recovery does not claim to fix the separate shared changelog command.
• Existing GitHub Release: https://github.com/atls/reactjs/releases/tag/%40atls/react-kratos%400.1.0. It is not proof of npm publication.
• Local preflight at the exact version commit: workspace selection was verified both without event context and with the original PR event; actionlint and yarn install --immutable passed. yarn workspace @atls/react-kratos pack produced a 0.1.0 tarball with dist/index.js and dist/index.d.ts; SHA-256 4e09d42e6f82714fdd8d082a243e9dea3a188f5bd79a54edaddb3c8b8574712c.
• No npm publish or manual dispatch was performed while preparing this PR.
• Publication verified: https://github.com/atls/reactjs/actions/runs/36631253525 completed successfully; npm serves @atls/react-kratos@0.1.0 with gitHead 9bc23729472414c56d1a0a2d67f423dec0f05cfc.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-29T20:07:24.196254Z	61ec368	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.