5a8cd32aec
Minimal harness for kind: customer_script nodes (agent-runtimes spec/tenant-namespaces.md SCR-1..SCR-6). No LLM turn - runs via the "shell" runner, agent-repo/v1 clone access only. Per-script credential needs are deliberately not baked into this base (SCR-6: narrow, per-script review) - compose a customer-script-<need>/v1 variant layering whichever specific credential context a given script actually needs, rather than widening this shared base. Without this commit, kind: customer_script was not dispatchable from any machine other than the one it was authored on - the harness lookup against a fresh CRS sync would fail. Claude-Session: https://claude.ai/code/session_012arAwUuBQrpnMzJ36mEVBk
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.