Skip to content

Publish v0.1.13 from the maintained fork - #1

Merged
BoldNewMedia merged 11 commits into
mainfrom
agent/maintained-fork-v0.1.13
Aug 17, 2026
Merged

Publish v0.1.13 from the maintained fork#1
BoldNewMedia merged 11 commits into
mainfrom
agent/maintained-fork-v0.1.13

Conversation

@BoldNewMedia

Copy link
Copy Markdown
Owner

Summary

Make BoldNewMedia/claude-plugin-codex the maintained release authority and publish the consolidated v0.1.13 release candidate through the fork.

  • includes the hardened v0.1.13 runtime and test work from the upstream release candidate
  • points public installation and manifest URLs at BoldNewMedia
  • identifies this repository as the maintained fork from v0.1.13
  • preserves the original MIT licence and Yanchuk attribution
  • keeps the marketplace name and plugin ID unchanged for compatibility
  • validates ownership-facing metadata and prevents the upstream install command from returning

Why

The upstream repository is not responding to issues or pull requests and forked Actions require upstream approval. Releases must not depend on an unavailable maintainer.

Checks

  • Node 24: 54/54 tests
  • plugin metadata validation: passed
  • installed Claude Code 2.1.201 smoke: passed
  • git diff --check: clean

The PR remains draft until fork-controlled Node 20/22/24 CI and the installed Codex-to-Claude E2E check pass.

Convert file URL references in the command and E2E tests with fileURLToPath instead of reading URL.pathname directly.

URL.pathname percent-encodes spaces, which makes child process invocations look for paths such as CLAUDE%20CODE... and fail with MODULE_NOT_FOUND. fileURLToPath preserves the correct filesystem path on local platforms.

Verified with the full test suite from the fork path and from a copied checkout under /private/tmp/claude plugin codex final space test.
Use path.dirname(fileURLToPath(import.meta.url)) for the E2E repo root instead of converting the parent directory URL directly.

This keeps the path-with-spaces fix while avoiding a trailing slash in the path passed as cwd and to codex exec --cd.
Use claude agents --json when monitoring background jobs so non-TTY Codex sessions can read lifecycle state and mark completed sessions done.

Also tolerate Claude JSON envelopes whose result string begins with Claude tool-call markup before the review JSON. Direct review payload validation remains strict so arbitrary leading prose is still rejected.

Tests cover agents JSON completion and tool-call-prefixed review output.
Handle Claude JSON envelopes whose result begins with status prose before the requested review JSON.

The direct review payload validator remains strict; this recovery is limited to Claude CLI envelope results. Adds a regression test for a result beginning with 'Now I have enough context to review.'
Add README guidance for CLAUDE_COMPANION_STATE_ROOT so sandboxed Codex environments can point companion state at a writable private directory.

Also note that the state root can contain prompts, Claude output, workspace paths, and review results, so it should stay local and out of version control.
Consolidate the path portability, review parser, monitor and state-root work from upstream PRs 2-4. Harden review diff collection, ambiguous JSON rejection, background cancellation and private state permissions. Make timeout tests deterministic, exercise the companion lifecycle in smoke tests, and update CI to current actions across Node 20, 22 and 24.
Run the nested Codex E2E with an explicit temporary companion state root so job state remains writable inside the sandbox. Keep manifest default prompts within Codex limits and validate those limits locally.
Allow the routing smoke to retain current Codex CLI diagnostics without terminating the nested session at Node's default one-megabyte spawn buffer.
Create the temporary companion state root within the checkout so nested Codex workspace-write policy permits lifecycle state, then remove it before asserting the worktree is unchanged.
Give the nested noninteractive Codex session only workspace-write access, keep companion state in a temporary checkout directory, and validate that the E2E harness retains this bounded sandbox.
Point installation and ownership metadata at BoldNewMedia while preserving the original MIT attribution. Document the fork governance boundary and validate the public release URLs and install source.
@BoldNewMedia
BoldNewMedia marked this pull request as ready for review August 17, 2026 14:08
@BoldNewMedia
BoldNewMedia merged commit b131e15 into main Aug 17, 2026
3 checks passed
@BoldNewMedia
BoldNewMedia deleted the agent/maintained-fork-v0.1.13 branch August 17, 2026 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant