fix(rate-limits): keep Codex PTY reset text for weekly-only plans - #8643

Process completed with exit code 1.

AssertionError: expected 'set -euo pipefail\n# Why: use npm ver…' not to contain 'generate-skill-bundle-manifest' - Expected + Received - generate-skill-bundle-manifest + set -euo pipefail + # Why: use npm version --no-git-tag-version so we control the commit + # message and tag name explicitly (avoids npm's `v1.2.3` prefix + # assumptions and any lifecycle scripts that would run on bump). + npm version "$VERSION" --no-git-tag-version --allow-same-version + # Why: release cut is the single authoritative point where the released + # skill ledger advances — this version's working-tree bytes become an + # immutable released revision so future builds recognize them as an + # official snapshot. It is the only place skill artifacts regenerate; + # ordinary lint verifies working-tree bytes against the committed ledger + # and never walks tags. Uses only Node built-ins, so no install needed. + node config/scripts/generate-skill-bundle-manifest.mjs --release "$VERSION" + git add package.json resources/skills + commit_message="release: v$VERSION" + if [[ "$EVENT_NAME" == "schedule" ]]; then + commit_message="$commit_message [rc-slot:$SLOT]" + fi + if git diff --cached --quiet; then + # Why: a failed cut can push the version bump to main before the + # release is published. Re-cutting then needs a fresh taggable + # release commit even though package.json is already at VERSION. + git commit --allow-empty -m "$commit_message" + else + git commit -m "$commit_message" + fi + git tag -a "v$VERSION" -m "v$VERSION" + echo "tag=v$VERSION" >>"$GITHUB_OUTPUT" + echo "sha=$(git rev-parse HEAD)" >>"$GITHUB_OUTPUT" + ❯ config/scripts/package-electron-runtime-contract.test.mjs:455:30

The `Function` type accepts any function-like value.

The `Function` type accepts any function-like value.

The `Function` type accepts any function-like value.

The `Function` type accepts any function-like value.

The `Function` type accepts any function-like value.

The `Function` type accepts any function-like value.

The `Function` type accepts any function-like value.

Do not use a reference value as the fill value.

Do not use a reference value as the fill value.