refactor(codex): clarify rate-limit parsing and refresh package docs #7

Merged

eleith merged 1 commits from refactor/codex-rate-limit-readability into main 2026-11-02 15:13:14 +00:00

Conversation 0 Commits 1 Files Changed 6

+106 -33

eleith-gitea-agent Bot commented 2026-11-02 15:10:57 +00:00

Copy link

Copy source

Status

Ready for owner review and landing. No further commits are currently planned in this PR. No 0.2.1 tag or publication has been performed.

Actual maintenance

• Separate private Retry-After parsing from HTTP error classification. Preserve the existing numeric/date coercion, finite/nonnegative checks and missing/empty-header behavior; no change to auth, endpoints, deadlines, byte limits, cancellation or retry policy.
• Replace the single 60-second usage regression with twelve named numeric/date/invalid/missing-header cases. Add a catalog HTTP-date case. Freeze time and assert sanitized errors, exactly one request, and error-body disposal through the public clients, without exporting internals or adding a testing framework.
• Correct the root README's old package name, broken link and feature summary.
• Correct the packaged README's heading, installation source, current context/fast on/off/toggle and usage commands, prefix example, and predecessor migration instructions. Preserve context baseline/cost/idle-replay cautions; explain fast eligibility, no-provider-override scope, requested-versus-observed tiers and terminal cancellation.
• Prepare 0.2.1 using a patch Changeset and generated version/changelog metadata. The release note describes this real maintenance, not merely OIDC configuration. Historical notes and unrelated manifest fields are unchanged.

Exactly six files change. No dependency, lockfile, workflow, provider/auth replacement or personal installation changes. The rejected version-only proposal is not included.

Verification

• Integrated code, readability and regression-test reviews: clear.
• Focused follow-up code/readability reviews of the approved packaged README correction: clear.
• 1,321 tests / 73 files passed.
• All extension builds, lint, typecheck, formatting, whitespace, consumed-release metadata and current README instruction validation passed on the final state.
• Fresh 0.2.1 tarball inspected: exactly LICENSE, dist/index.js, package.json, CHANGELOG.md and README.md; expected version/entrypoint, no runtime/optional dependencies or workspace references. Bundle and packaged documentation match current build/source bytes. No disposable npm consumer installation test.

Publication after landing

The owner wants the next GitHub Actions publish to establish the newly configured npm trusted publisher before its initial validation window expires. This patch contains genuine readability, regression-test and documentation work rather than a release-only bump.

After owner landing and separate release-tag authorization, use @eleith-pi/codex@0.2.1 at the landed release commit. Do not manually npm-publish 0.2.1: the GitHub codex.yml publish step must execute successfully, not skip an existing version, to validate OIDC. The tag also triggers private Gitea publication.

The 0.2.0 tag is confirmed on GitHub and its workflow succeeded, but that already-published version did not validate a new OIDC publish. Public npm 0.2.1 returned 404 before preparation; recheck before tagging. Do not claim OIDC validation based only on an overall green workflow.

Owner controls landing and release authorization. No tag, publication, token handling or trusted-publisher changes performed in this PR.

## Status Ready for owner review and landing. **No further commits are currently planned in this PR.** No 0.2.1 tag or publication has been performed. ## Actual maintenance - Separate private `Retry-After` parsing from HTTP error classification. Preserve the existing numeric/date coercion, finite/nonnegative checks and missing/empty-header behavior; no change to auth, endpoints, deadlines, byte limits, cancellation or retry policy. - Replace the single 60-second usage regression with twelve named numeric/date/invalid/missing-header cases. Add a catalog HTTP-date case. Freeze time and assert sanitized errors, exactly one request, and error-body disposal through the public clients, without exporting internals or adding a testing framework. - Correct the root README's old package name, broken link and feature summary. - Correct the packaged README's heading, installation source, current context/fast on/off/toggle and usage commands, prefix example, and predecessor migration instructions. Preserve context baseline/cost/idle-replay cautions; explain fast eligibility, no-provider-override scope, requested-versus-observed tiers and terminal cancellation. - Prepare **0.2.1** using a patch Changeset and generated version/changelog metadata. The release note describes this real maintenance, not merely OIDC configuration. Historical notes and unrelated manifest fields are unchanged. Exactly six files change. No dependency, lockfile, workflow, provider/auth replacement or personal installation changes. The rejected version-only proposal is not included. ## Verification - Integrated code, readability and regression-test reviews: **clear**. - Focused follow-up code/readability reviews of the approved packaged README correction: **clear**. - **1,321 tests / 73 files passed.** - All extension builds, lint, typecheck, formatting, whitespace, consumed-release metadata and current README instruction validation passed on the final state. - Fresh 0.2.1 tarball inspected: exactly LICENSE, dist/index.js, package.json, CHANGELOG.md and README.md; expected version/entrypoint, no runtime/optional dependencies or workspace references. Bundle and packaged documentation match current build/source bytes. No disposable npm consumer installation test. ## Publication after landing The owner wants the next GitHub Actions publish to establish the newly configured npm trusted publisher before its initial validation window expires. This patch contains genuine readability, regression-test and documentation work rather than a release-only bump. After owner landing and separate release-tag authorization, use `@eleith-pi/codex@0.2.1` at the landed release commit. **Do not manually npm-publish 0.2.1**: the GitHub `codex.yml` publish step must execute successfully, not skip an existing version, to validate OIDC. The tag also triggers private Gitea publication. The 0.2.0 tag is confirmed on GitHub and its workflow succeeded, but that already-published version did not validate a new OIDC publish. Public npm 0.2.1 returned 404 before preparation; recheck before tagging. Do not claim OIDC validation based only on an overall green workflow. Owner controls landing and release authorization. No tag, publication, token handling or trusted-publisher changes performed in this PR.

eleith-gitea-agent Bot added 1 commit 2026-11-02 15:10:57 +00:00

refactor(codex): clarify rate-limit parsing and refresh package docs ... 7601c707b0

Separate Retry-After interpretation from HTTP error classification without changing accepted delays. Characterize numeric, date, invalid and absent headers through public account clients, retaining no-retry and error-body cleanup assertions.

Correct Codex installation, controls and migration documentation, and prepare 0.2.1 with a Changesets-generated maintenance entry.

eleith merged commit 7601c707b0 into main 2026-11-02 15:13:14 +00:00

eleith deleted branch refactor/codex-rate-limit-readability 2026-11-02 15:13:14 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

bug

Something is not working

duplicate

This issue or pull request already exists

enhancement

New feature

help wanted

Need some help

invalid

Something is wrong

question

More information is needed

wontfix

This won't be fixed

No labels

Milestone

No items

No Milestone

Assignees

Clear assignees

eleith-gitea-agent Bot eleith (eleith)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: eleith/pi-extensions#7