docs(rfc): RFC 0013 - infrastructure-level observability

[rhuss]

Summary

Proposes extending OpenShell's infrastructure observability to the components that have no OTel coverage today. Rooted in four persona workflows (platform operator, CI engineer, security reviewer, platform integrator).

• In-process driver instrumentation (K8s, Docker, Podman) following the VM driver pattern
• Passive CLI TRACEPARENT forwarding for CI pipeline trace continuity
• OCSF-to-OTel correlation via trace_id/span_id fields
• Helm OTLP deployment configuration (gateway.toml + Helm values)
• Prometheus metrics maturity path from RED basics to the full feat(server): metrics instrumentation #909 catalog

All work builds on existing foundations (merged gateway/VM driver OTLP, openshell-otel crate, OCSF, Prometheus). No new transport mechanisms or architectural novelty.

Related issues

• #1055 - Enterprise Observability
• #2507 - Gateway OTel export surface
• #909 - Metrics instrumentation

Note on RFC number

RFC number 0013 is provisional. Per the RFC process, maintainers assign numbers from an issue. This PR uses the next available number; please reassign if needed.

Split from PR #2620 (RFC 0012) based on maintainer feedback. Agent-level observability (the OTLP relay) is covered in a companion RFC 0014.

Test plan

• Review RFC content for technical accuracy
• Verify persona workflows match real operator/integrator needs

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[rhuss]

Closing this PR. I overlooked the process documented in rfc/README.md: features start as GitHub issues, and RFCs are only created when maintainers request one from an existing issue. Apologies for skipping that step.

The content from this RFC is being reformed as GitHub issues linked to the Enterprise Observability umbrella (#1055). Most of the infra-level observability work is already tracked by #2507 (gateway OTel export surface) and #909 (metrics instrumentation). New issues will cover the gaps: CLI passive trace propagation and OCSF-to-OTel correlation fields.

The branch is kept for reference.