fix: bump pctx_code_mode to 0.3.0 for iterator type checking fix

[spitfire55]

Summary

• Bumps pctx_code_mode from ^0.2.3 to ^0.3.0
• Fixes false-positive TS2488 errors that cause execute tool calls with for...of loops to fail

Problem

The execute tool uses pctx's TypeScript type checker before running code. With pctx_code_mode 0.2.3 (which depends on pctx_type_check_runtime 0.1.2), the type checker uses a minimal lib.d.ts that doesn't include ES2015 iterable definitions (lib.es2015.iterable.d.ts).

This means any code using for...of on an array fails type checking with:

TS2488: Type '{}' must have a '[Symbol.iterator]()' method that returns an iterator.

Even though arrays are perfectly iterable at runtime. When this happens, the execute tool aborts before execution, and the model has to fall back to making individual tool calls instead of batched operations.

Example of valid code that fails:

const files = ['a.go', 'b.go', 'c.go'];
for (const f of files) {  // TS2488 error here
    await Developer.shell({ command: `cat ${f}` });
}

Fix

pctx_code_mode 0.3.0 depends on pctx_type_check_runtime 0.1.3, which includes full ES2020+ lib files (including lib.es2015.iterable.d.ts). This was fixed upstream in portofcontext/pctx@db67183 ("include ts lib deps as part of type checking").

Test plan

• Verify execute tool calls with for...of loops no longer fail type checking
• Verify existing execute tool functionality is unaffected

🤖 Generated with Claude Code

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 03e04e2153

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Regenerate Cargo.lock after bumping pctx_code_mode

This manifest change alone does not update the repository’s resolved dependency set: in this revision, Cargo.lock still pins pctx_code_mode to 0.2.3 (and pctx_type_check_runtime to 0.1.2), so the intended type-checking fix is not actually captured in committed sources that rely on the lockfile; in lockfile-driven/frozen build contexts, this either keeps the old behavior or fails because the lock is stale.

Useful? React with 👍 / 👎.