bf18ca3ef5
Probe 6 (2026-05-08) showed git push failing twice with exit 1 and zero visible output — the previous form `if cmd 2>&1; then` redirected git's stderr to stdout where the entrypoint's stderr-only log capture missed it. CP-side log showed only the bash `set -x` trace, not the actual git error message (e.g., "Permission denied (publickey)" or "remote: pre-receive hook rejected"). Refactor the push retry loop: - Capture output to PUSH_OUT via $() with `2>&1` - Wrap in set +e/set -e to detect non-zero without aborting - echo PUSH_OUT to stderr (where set -x trace also goes) so the entrypoint's stderr capture sees it 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.