You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: standardize all markdown links to use .md extension
Bulk-convert 553 internal links across 72 documentation files from
.html to .md extension. Markdown files now link to .md (rendered by
GitHub natively), while HTML <a> tags retain .html (for GitHub Pages).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/CHANGELOG.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,28 +19,28 @@ All issues found and fixes applied during the 5 review cycles of the ModelMesh L
19
19
20
20
| File | Issue | Fix |
21
21
| --- | --- | --- |
22
-
|`SystemConcept.md`| Referenced `ProviderSchemas.md` which does not exist (lines 101, 248) | Replaced with `[Provider Interface](interfaces/Provider.html)` and removed redundant footer reference |
22
+
|`SystemConcept.md`| Referenced `ProviderSchemas.md` which does not exist (lines 101, 248) | Replaced with `[Provider Interface](interfaces/Provider.md)` and removed redundant footer reference |
Copy file name to clipboardExpand all lines: docs/ConnectorCatalogue.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,9 +5,9 @@ title: "Connector Catalogue"
5
5
6
6
# Connector Catalogue
7
7
8
-
**Pre-shipped connector implementations for ModelMesh Lite.** Each section lists available implementations for one connector type. Individual connector documentation is in [connectors/](connectors/openai-llm.html). Interface definitions are in [ConnectorInterfaces.md](ConnectorInterfaces.html). Custom connectors implement the same interfaces and register in the same catalogue (see [Developer Manual](SystemConcept.html#connector-based-extensibility)).
8
+
**Pre-shipped connector implementations for ModelMesh Lite.** Each section lists available implementations for one connector type. Individual connector documentation is in [connectors/](connectors/openai-llm.md). Interface definitions are in [ConnectorInterfaces.md](ConnectorInterfaces.md). Custom connectors implement the same interfaces and register in the same catalogue (see [Developer Manual](SystemConcept.md#connector-based-extensibility)).
9
9
10
-
> **Building custom connectors?** The [Connector Development Kit](cdk/Overview.html) provides base classes and tutorials for creating new connectors with minimal code.
10
+
> **Building custom connectors?** The [Connector Development Kit](cdk/Overview.md) provides base classes and tutorials for creating new connectors with minimal code.
11
11
12
12
> Pricing and availability change frequently; consult each provider's documentation for current details.
13
13
@@ -36,13 +36,13 @@ In YAML configuration, the `connector_type.` prefix is omitted within its own se
Provider connectors (OpenAI, Anthropic, and others) declare model capabilities using **dot-notation paths** that reference the [capability hierarchy](ModelCapabilities.html). Short-form capability names (`"chat"`, `"tools"`, `"vision"`) are no longer used; capabilities now map directly to tree nodes such as `generation.text-generation.chat-completion`. Features like tool calling, vision, and system prompt support are declared separately in a `features` dict.
45
+
Provider connectors (OpenAI, Anthropic, and others) declare model capabilities using **dot-notation paths** that reference the [capability hierarchy](ModelCapabilities.md). Short-form capability names (`"chat"`, `"tools"`, `"vision"`) are no longer used; capabilities now map directly to tree nodes such as `generation.text-generation.chat-completion`. Features like tool calling, vision, and system prompt support are declared separately in a `features` dict.
46
46
47
47
**Before (short-form, deprecated):**
48
48
@@ -69,7 +69,7 @@ The provider-level `capabilities` config follows the same convention. For exampl
69
69
70
70
### Pool Definition Modes
71
71
72
-
Pools support three definition modes (see also [SystemConfiguration.md -- Pools](SystemConfiguration.html#pools)):
72
+
Pools support three definition modes (see also [SystemConfiguration.md -- Pools](SystemConfiguration.md#pools)):
73
73
74
74
| Mode | Config Fields | Behaviour |
75
75
| --- | --- | --- |
@@ -240,7 +240,7 @@ Non-AI web services can be wrapped as provider connectors using the same interfa
Both classes expose the same provider interface and the same protected hooks for subclassing. See [cdk/BaseClasses](cdk/BaseClasses.html#browserbaseprovider) for details and [guides/BrowserUsage](guides/BrowserUsage.html) for browser setup.
243
+
Both classes expose the same provider interface and the same protected hooks for subclassing. See [cdk/BaseClasses](cdk/BaseClasses.md#browserbaseprovider) for details and [guides/BrowserUsage](guides/BrowserUsage.md) for browser setup.
Audio requests are internally bridged to `CompletionRequest`/`CompletionResponse` via the `AudioRequest` and `AudioResponse` types (see [ConnectorInterfaces.md -- Audio](ConnectorInterfaces.html#audio)). The same rotation, failover, and pool logic applies to audio providers.
293
+
Audio requests are internally bridged to `CompletionRequest`/`CompletionResponse` via the `AudioRequest` and `AudioResponse` types (see [ConnectorInterfaces.md -- Audio](ConnectorInterfaces.md#audio)). The same rotation, failover, and pool logic applies to audio providers.
294
294
295
295
---
296
296
297
297
## Rotation Policies
298
298
299
-
Interface: [ConnectorInterfaces.md — Rotation Policy](ConnectorInterfaces.html#rotation-policy). Full attributes in [SystemConfiguration.md — Pools](SystemConfiguration.html#pools).
299
+
Interface: [ConnectorInterfaces.md — Rotation Policy](ConnectorInterfaces.md#rotation-policy). Full attributes in [SystemConfiguration.md — Pools](SystemConfiguration.md#pools).
The observability interface combines four concerns: **events** (state changes), **logging** (request/response data), **statistics** (aggregate metrics), and **tracing** (severity-tagged structured traces). All core components (Router, Pool, Mesh) and CDK base classes (BaseProvider) emit traces through the configured observability connector. If no connector is configured, the `null` connector is used (zero overhead).
540
540
@@ -640,7 +640,7 @@ All observability connectors write records with a `"type"` field. The file conne
0 commit comments