Implementation Plan: T5-P3-A3-WP1 Establish Committed Fixture Foundation for B3a Deterministic Conformance#4137
Merged
Trecek merged 3 commits intoJun 28, 2026
Conversation
Establish tests/execution/backends/fixtures/codex_ndjson/ as the home for B3a deterministic conformance JSON Schema fixtures. The package exports FIXTURE_SCHEMA_VERSION and fixture_schema_path() helper. Also registers the new fixtures glob in .autoskillit/test-filter-manifest.yaml so changes to any codex_ndjson JSON file trigger the execution/ test path.
Add 19 JSON Schema draft-7 fixtures that bijectively cover the non-UNKNOWN members of CodexEventType (9 schemas) and CodexItemType (10 schemas). Each schema declares additionalProperties: false to seal the parser contract boundary; new CLI-emitted fields trigger a fixture refresh review per B3a requirements. Event schemas encode the parser-required keys per type (thread_id, payload.id, item, usage, error, etc.), and item schemas encode sub-object shapes for agent_message, message, file_change, and the 7 minimal-payload item types.
Seal two derived-data fixtures for B3a conformance: * hook_event_format_snapshot.json — captures generate_codex_hooks_config() output keyed by _registry_hash bound to HOOK_REGISTRY_HASH. Trusted hashes are sanitized to a deterministic sentinel and command paths replaced with a placeholder so the fixture is portable across hosts. * config_toml_schema_template.json — declares the four CODEX_MCP_REQUIRED_KEYS with their expected Python types and the two top-level token limit floors (tool_output_token_limit >= 50000, model_auto_compact_token_limit >= 999999999) using a 'constraint: minimum' annotation so WP3 conformance tests compare with >= rather than equality.
Trecek
force-pushed
the
t5-p3-a3-wp1-establish-the-committed-fixture-foundation-for/4010
branch
from
035f992 to
54416ec
Compare
Trecek
deleted the
t5-p3-a3-wp1-establish-the-committed-fixture-foundation-for/4010
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Create 21 committed JSON fixture files and 2 Python package init files under
tests/execution/backends/fixtures/codex_ndjson/to seal the contract boundary between Codex CLI NDJSON output and the production parser. This includes 9 event schemas (one per non-UNKNOWNCodexEventType), 10 item schemas (one per non-UNKNOWNCodexItemType), a hook event format snapshot bound toHOOK_REGISTRY_HASH, and a config.toml schema template. Also updates.autoskillit/test-filter-manifest.yamlwith a glob pattern for the new JSON fixture files. No source code or test files are modified — this WP produces only fixture data consumed by P3-A3-WP3's conformance tests.Closes #4010
Implementation Plan
Plan file:
/home/talon/projects/autoskillit-runs/impl-20260628-005721-828122/.autoskillit/temp/make-plan/t5-p3-a3-wp1-establish-fixture-foundation_plan_2026-06-28_010600.md🤖 Generated with Claude Code via AutoSkillit
Token Usage Summary
* Step used a non-Anthropic provider; caching behavior may differ.
Token Efficiency
Model Usage Breakdown