Developer integrations

This is a proposed direction, not an available feature or a delivery commitment. No release date is assigned.

Operator problem

Developers need stable context when handing an application failure to an operator.

Current alpha boundary

OTel application guides, controlled APIs and exact-window investigation links provide current entry points. External MCP compatibility and an arbitrary plugin market are not alpha promises. See the current operator guide.

Proposed capability

Study one documented read-only developer integration that carries service identity, time and source references.

Evidence required

Prove malformed links, expired sessions, missing identity, route compatibility and cancellation without losing original query semantics.

Non-goals

No IDE-wide parity, remote shell execution or undocumented credential propagation.

Contribution entry

Bring a concrete workflow and a reproducible failure to the contribution process. Agree the smallest contract and acceptance evidence before implementation. Return to the roadmap.