v3.37.0 — Receiver fixes and runner pin

Theme: Receiver fixes and runner pin.

For: supervisors and maintainers upgrading Agets from v3.36.0.

What's New

• Scratch tests stay isolated. In core and templates, tests clear inherited git-location variables, including GIT_CONFIG, before collection and stop upward discovery at the temporary root. Template item M-3.37-6 includes this isolation and its source test.
• Scope approval cannot authorize launch. Active/archived scope records are checked; old-format records block launch until retired. Prompts cover staging new, non-ignored protected files without editing them.
• Receiver adoption checks ship. Policy review, pre-upgrade fleet-skew and post-apply halt checks become explicit; test-body skips are reported with limits below.
• CI pins its runner and actions. Core uses Ubuntu 24.04, checkout v7 and setup-python v7; template copies filter compiled caches.
• Payload gates inspect different trees. python3 verification/validate_release_gate.py 3.37.0 --payload-only --framework-path <framework-root> reads each template's complete tree at the tag. python3 scripts/check_tag_payload_coherence.py --version 3.37.0 --pre-tag reads only the committed subtree under its working directory or --cwd; run from the repository root or pass that root as --cwd.
• Wind-down health is visible. In core and templates, timeouts report TIMEOUT and crashes ERROR; a nonzero health-process exit cannot hide behind PASS JSON.

Compatibility

No public interface removal is declared. Launch and compiled-cache refusals tighten acceptance. Install the kit from pinned core, separately from templates; its python3 must import PyYAML and pytest. Follow the core release notes, migration message, handoff and CHANGELOG.
After seeding, complete Wave Sequencing / Wave-0 Supervisor Self-Upgrade, steps 1–3, before Wave 1. Read v3.37.0 corrections if present.

Disclosed Limitations

• The producer payload gate has no automatic caller in the release path; run it by hand per docs/RELEASE_PAYLOAD_GATE.md. Producer wiring is a separate obligation; see payload-gate limits.
• The kit changes only root @aget-version; see separately reviewed specification-pin updates outside the batch/after-run window and root halt-check limits.
• Read the Health Gate line; see UNKNOWN and the test of screen text only.
• See escaped timeout descendants and five extra seconds of pipe draining. Use core's docs/protocols/WIND_DOWN_PROTOCOL.md; smoke-check receiver health observations and timeout configuration.
• See test-body witness misclassification and Python requirements before relying on completion reports.
• See scope archive, retirement, seeding and trust limits before resuming launches.
• Inspect retained external symlinks before instantiation or deployment; see symlink containment.
• See runner qualification, hosted CI and older kit limits; earlier v3.36.0 notes and corrections apply unless repaired here.

Read Known limitations and disclosures and the release notes' evidence limits before relying on local results.

Deferred

Template close-authorization guard repair is deferred again to the next release, owned by the release manager; follow v3.35.0 corrections, rows 4–5 until a template tag carries it.