v4.2.1 — TaskCreated hook tolerates stringified metadata - #62
Merged
Merged
Conversation
The Claude Code harness sometimes delivers tool_input.metadata as a JSON-encoded string rather than an object. The original jq path .tool_input.metadata.user_story silently returned empty in that case, rejecting valid TaskCreate calls with "required metadata is missing or invalid". Normalize first: if metadata is a string, parse it via fromjson?; otherwise pass through. Same downstream validation either way. Verified across five payload shapes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
scripts/task-created-tag-check.shrejected valid TaskCreate calls when the Claude Code harness deliveredtool_input.metadataas a JSON-encoded string instead of an object. Thejqpath.tool_input.metadata.user_storysilently returned empty in that case, even though the caller supplieduser_story/layercorrectly.metadatabefore extracting fields — if it's a string, parse viafromjson?; otherwise pass through. Same downstream validation either way (US-<N>/AC-<N>.<M>/chore:<reason>plus the Rust layer check).US-1+AC-1.2), empty payload, bogus tag. Accepted shapes pass; invalid shapes still reject with the original error.Test plan
🤖 Generated with Claude Code