Skip to content

[Workstream N] PR 5 of 6: Codex commandWindows entries and additionalContextLimit #188

Description

@zaxbysauce

Part of #100 (EPIC). Workstream N. One issue = one PR.
Source: zmem deep audit 2026-09-10 (https://claude.ai/code/artifact/39012f75-25f0-441b-978f-cc90a3bd3a9d) and issue plan v3 (https://claude.ai/code/artifact/59e74242-17da-4416-9b00-0b0cf347837c); dependency DAG computed over all open PRs (edge kinds: Depends on = merged artifact, Schema after = migration lane, Gated on = #100 measurement/decision gate).

Labels: bug, severity:medium. Depends on: N-3 (#186) (resolveShell()). Blocks: #96.

Design. Every Codex entry gains commandWindows calling node with an absolute ${PLUGIN_ROOT} path and no nested quoting, and additionalContextLimit from one constant equal to CODEX_ENVELOPE_CAP_BYTES / CHARS_PER_TOKEN rounded down (2,000). Docs are #127; the desktop re-trust canary is #96.

Acceptance criteria. (a) Manifest test: every context-bearing Codex entry has commandWindows and additionalContextLimit == 2000, and the constant equals floor(8000/4) by import. (b) tests/test_codex_adapter.js drives each verb through the Windows command string on test-windows against committed expected envelopes. (c) tests/test_release_parity.py passes.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingseverity:mediumMedium-severity finding from codebase review

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions