Replies: 1 comment
|
Update: the reproducible canary is now available as a public npm package and GitHub release. The published run resolves the Codex version pinned by the official Harness source, generates the baseline and target Codex App Server schemas, and compares only protocol values the adapter explicitly consumes. It is read-only with respect to Harness and does not use model or DeepSeek credentials. Current public-package result:
Validation: 16 tests pass, cross-platform CI is green, and installation plus the live check were verified from the public npm registry. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
DeepSeek Harness
@deepseek-ai/dsh-subagent-codex@0.1.1-rc.2pins@openai/codex@0.147.0. Testing the same integration contract against Codex0.149.1found one newCodexErrorInfostring member,misalignmentPolicyViolation. The current adapter's explicit string allow-list does not include it, sofailureInfo()returnsunknownfor that terminal failure.中文摘要：当前 Codex 子代理固定使用
0.147.0。Codex0.149.1新增错误分类misalignmentPolicyViolation，而 Harness 的显式映射尚未包含它，因此该失败会被降级显示为unknown。下面的复现不需要模型凭证，并已验证最小映射修复能恢复原始分类。Reproduction
Fixed inputs:
b150a551b8d465e31e418e1b2eaf5e79bbb7d28e@deepseek-ai/dsh-subagent-codex@0.1.1-rc.20.147.00.149.1Observed evidence:
0.147.0baseline.0.149.1, the schema-evidence assertion detects the new enum member.misalignmentPolicyViolationto the existing complete-string-union unit case fails against production code: expected the category name, receivedunknown.casetofailureInfo()makes the focused regression pass.Codex schema inventory changed from 285 to 291 JSON files: 6 added, 45 shared files changed, none removed. No server-request method was added between these versions.
Minimal compatibility decision
Preserve
misalignmentPolicyViolationalongside the other string categories infailureInfo()and include it in the complete-union test when the pinned Codex dependency is upgraded. The existing safe diagnostic already emits only the category name, so this does not require copying upstream message text or new fields.Reusable canary
I published a small external checker with the complete report and fixtures:
It compares generated Codex error variants and newly added server-request methods with the exact cases handled by the Harness adapter. It does not execute Harness source, call a model, read credentials, modify a profile, or treat every schema diff as breaking.
I also checked the new
dsh-compat-guarddiscussion. That project gates Harness/plugin upgrades and protects user data with compatibility metadata, snapshots, migration, and rollback. This report is narrower and complementary: it checks external Codex App Server protocol values against the official in-tree Codex adapter, without performing or gating a Harness upgrade.Since the contribution guide currently says external pull requests are not accepted, I am reporting the tested change here rather than opening a PR. I would appreciate confirmation of whether this category should be preserved in the next Codex dependency update and whether this style of compatibility report is useful to maintainers.
All reactions