Task · SKT-0210

Reject the legacy throttle switch on causally bound agent runtimes

Description

Owner ruling Q10 (loop58): a bound agent runtime silently ignores the region-scoped legacy agentcore_throttle mode, so a story using it does nothing. Make blueprint load reject that switch on bound runtimes (guarded loader hook). The deployment-wide global series stays.

Acceptance Criteria

Definition of Done

Implementation Plan

Add loader rejection for legacy throttle targeting a causally bound agent runtime, retain unbound and deployment-global behavior, and prove via public blueprint load plus scoped gates.

Loop60: complete selected AgentCore bound/unbound public CLI inventory and sourced conformance, with existing source unchanged.

Implementation Notes

Two failed review rounds opened integration-fixture and authored/effective-scope mismatch classes. First convergence tripwire selected senior escalation and a fail-closed schedule-representability approach; no landing acceptance yet.

Source published at 9d8185727522f30e8eb7b731ff7f3f8c293904db in exact-gated dac0d2b4139b5fc851a49f2b16c77a5dadd15421. Native guarded PASS and loader/CLI rejection/compatibility retained. Required selected AgentCore CLI inventory/conformance was not run: reviewer lacked required wait helper. Resume with that public-entrypoint proof, not unit-test substitution. Hosted CI independently red; owner ended run without repair push.

Selected bound/unbound public CLI inventory gap closed: exact 60/60 AgentCore metric names and raw label regimes, nonempty app/usage logs, 457/457 names conformance with no parse gaps, expected bound loader rejections and genuine checker negative controls. Relevant published source unchanged. Offline inventory is not numerical backend or vendor verification.

View the source file on GitHub