docs: add Runtime Authoring Guide

[JAORMX]

This PR adds a new implementation-agnostic Runtime Authoring Guide.

Key points:

• Defines a stable behavioral contract for new runtimes (capabilities, lifecycle, transports, permissions, isolation, labels, idempotency, error handling, observability, testing, security posture, performance, portability, and acceptance criteria).
• Adds an appendix clarifying the runtime obligations for MCP_TRANSPORT and MCP_PORT (and compatible FASTMCP_PORT/MCP_HOST), including precedence and merge strategy, isolated vs non-isolated behaviors, and separation of internal MCP_PORT vs externally published host port.

Document path:

• docs/runtime-implementation-guide.md

This should help future runtime authors implement consistent behavior across platforms while leaving room for platform-specific optimizations.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 46.94%. Comparing base (b92b9e7) to head (1659d3d).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1890      +/-   ##
==========================================
- Coverage   47.01%   46.94%   -0.08%     
==========================================
  Files         223      223              
  Lines       27659    27669      +10     
==========================================
- Hits        13005    12989      -16     
- Misses      13653    13684      +31     
+ Partials     1001      996       -5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[coveralls]

coverage: 42.926% (+0.04%) from 42.885%
when pulling e956dff on docs/runtime-authoring-guide
into 736602f on main.

[coveralls]

coverage: 42.882% (-0.003%) from 42.885%
when pulling e956dff on docs/runtime-authoring-guide
into 736602f on main.

[eleftherias]

Is List part of the workload lifecycle? We have a similar section on listing above in the Runtime contract section, I wonder if we need it in both places.