e89208f44b
All 6 concept/idea-stage templates hardcoded the literal shared branch
spec/auto-draft instead of a per-item branch. Concurrent concept items
(now routine via the M41 auto-advance sweep) all pushed to the same
branch — a git collision risk. Switched to spec/${item.uuid}, matching
the established task/${item.uuid} convention used by every task-stage
template (merge@1, scaffold@1, etc — see spec/typed-workflows.md WF-COMP
stable-per-item-branch rationale). spec-review-loop@1's 4 nodes keep the
literal branch shared ACROSS the node set (now per-item, not global) so
loop iterations still accumulate on one branch per item, per spec's
cross-iteration-artifact caveat.
Files: review-spec-arch-opus@1.yaml, spec-draft-opus@1.yaml,
spec-review-loop@1.yaml, review-spec-arch-airouter@1.yaml,
spec-draft-airouter@2.yaml, scope-decompose-sonnet@1.yaml
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.