feat: Add origin header to ThreadContext::HeaderIdBundle for internal…

[tewaro]

… use

[ask-bonk]

I'm Bonk, and I've done a quick review of your PR.

This PR adds an origin (Origin) header ID to ThreadContext::HeaderIdBundle.

Issues (ranked by severity):

1. [MEDIUM] No usages of the new field. The origin header ID is registered in the bundle but is not referenced anywhere in the codebase. Every other field in HeaderIdBundle has a comment documenting its purpose (e.g., // used by cache API implementation, // used in tracing instrumentation). Without a consumer, this is dead code — it increases the header table size for every thread context with no benefit. Could you either (a) add the code that uses it in this PR, or (b) explain the intended consumer so reviewers can evaluate whether this addition is appropriate?

2. [LOW] Missing usage comment. All other fields in the struct have a // used by … comment. The new field should follow the same convention.

See inline comments for details.

---

This review was generated by an AI assistant and may contain errors. Please verify all suggestions before applying.

[ask-bonk]

I'm Bonk, and I've done a quick review of your PR.

This PR adds an Origin header ID to ThreadContext::HeaderIdBundle. I posted a review with two findings:

1. [MEDIUM] No usages of the new field. The origin header ID is registered but never referenced anywhere in the codebase. Without a consumer, this is dead code that increases the header table size for every thread context. The PR should either include the code that uses this field or explain the intended use case.

2. [LOW] Missing usage comment. Every other field in HeaderIdBundle has a // used by … comment documenting its purpose. The new field lacks one.

Review posted at: #6297 (review)

github run