79f00b566d
The agent-runtimes repo is moving to a CRS-only harness model: dispatcher images stop baking in /app/harnesses/ and discover them via CRS at runtime. cp-harness was the only harness that lived only in the agent-runtimes checkout (created in M16 Phase 1 D4, commit c1df4cc) — copied here so nothing is lost in the cutover. cp-harness has no current consumers (no composite or template references it); it is infrastructure for the future M16 self-orchestration api_key submission flow. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
agent-runtime-framework
Framework reference config repo for the agent-runtimes platform.
This repo is attached at CP scope with tags [harnesses, templates, workflows, model-registry, models]
and provides the default content that all installations inherit.
Contents
harnesses/— capabilities, contexts, compositestask-templates/— dispatch-task template YAMLsworkflows/— workflow DAG definitionsmodel-registry/— model scoring YAMLsmodels/— model endpoint YAMLs
Usage
Registered as a CRS attachment at CP scope (priority 100). Customer installations attach their own repos at lower priority to override or extend.