Add specs for custom webhook headers

[ogenstad]

Why

Adds specifications for Spec Kit for custom webhook headers INFP-INFP-445

What changed

• Added markdown files for webhook specification

How to review

• Consider the filename of the spec folder, currently it uses an integer and short name of the feature. This is the Spec Kit default. Other options include using a date as we've done in the past. Alternatively we could reference the epic in Jira.
• I opted for using the key value pair for generic and nodes instead of the initial suggestion to have a generic for HTTP headers. I figured that this approach is more general and could possibly apply to other things as well
• Review and match with regards to expectation of the feature

Summary by CodeRabbit

• Documentation
  • Added comprehensive specification for custom HTTP headers on webhooks, including user stories, functional requirements, error handling, and acceptance criteria for the planned feature.
  • Added specification quality checklist to validate webhook headers feature requirements and readiness.

[coderabbitai]

Walkthrough

Two new specification documents were added to the dev/specs/001-webhook-headers/ directory. The first introduces a specification quality checklist containing validation criteria across Content Quality, Requirement Completeness, and Feature Readiness sections, with all items marked as completed. The second establishes a comprehensive feature specification for custom HTTP headers on webhooks, detailing four user stories, functional requirements including key-value pair creation, many-to-many webhook associations, environment variable resolution, masking of sensitive values, and acceptance criteria for end-to-end testing. Both documents include metadata and references to related specifications.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Add specs for custom webhook headers' accurately and clearly summarizes the primary change in the pull request—adding specification files for custom webhook headers feature.
Description check	✅ Passed	The description addresses the Why section with issue reference and covers What changed and How to review. However, several template sections are missing including behavioral changes, implementation notes, testing instructions, and impact/rollout considerations.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

dev/specs/001-webhook-headers/spec.md (1)

81-81: Consider specifying the header count threshold.

The edge case mentions "a very large number of custom headers" requiring an upper bound. For clarity, consider either defining a specific threshold in the requirements section (e.g., "System SHOULD enforce a limit of 50 custom headers per webhook") or noting that the threshold will be determined during implementation based on performance testing.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@dev/specs/001-webhook-headers/spec.md` at line 81, Update the spec
001-webhook-headers to explicitly state a header-count limit: add a requirement
under the webhook custom headers section that the system SHALL enforce a maximum
of 50 custom headers per webhook (or alternatively add a note that the threshold
will be determined by performance testing and risk assessment if you prefer not
to lock a number now); reference the spec ID "001-webhook-headers" and the
phrase "custom headers" so implementers know where this limit applies.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@dev/specs/001-webhook-headers/spec.md`:
- Line 81: Update the spec 001-webhook-headers to explicitly state a
header-count limit: add a requirement under the webhook custom headers section
that the system SHALL enforce a maximum of 50 custom headers per webhook (or
alternatively add a note that the threshold will be determined by performance
testing and risk assessment if you prefer not to lock a number now); reference
the spec ID "001-webhook-headers" and the phrase "custom headers" so
implementers know where this limit applies.