Skip to content

Keep the Codex processor fixture as the first JSON example - #4

Closed
geldmacher wants to merge 1 commit into
mainfrom
dg-cursor/codex-fixture-json-order-b9a7
Closed

geldmacher wants to merge 1 commit into
mainfrom
dg-cursor/codex-fixture-json-order-b9a7

Conversation

@geldmacher

@geldmacher geldmacher commented Oct 2, 2026 •

Copy link
Copy Markdown
Owner

Summary

The Validate job reads the first json fence in skills/rtk-setup/references/codex.md as the RTK processor fixture. The hook metadata example added in ffdb77c became that first fence, so hook_event_name was undefined and documented RTK processor fixtures include each host's required input fields failed.

Move Processor and live execution ahead of Hook metadata and trust. The processor payload (hook_event_name, tool_name, permission_mode) is the first json fence again. The metadata handler example and the #hook-metadata-and-trust link stay intact. Assertions are unchanged.

Test plan

Open in Web Open in Cursor 

The release check reads the first JSON fence in the Codex RTK reference as the processor fixture. The hook metadata example was added above it, so hook_event_name was missing. Move Processor and live execution ahead of Hook metadata and trust.

Co-authored-by: Dennis Geldmacher <geldmacher.dennis@outlook.de>
@geldmacher geldmacher closed this Oct 2, 2026
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.

2 participants