# Git History — output of git-historian

Task: Add a per-wave concurrency cap to trekexecute headless launches.

## Recent changes touching the launch path

| Commit (illustrative) | Area | Relevance |
|-----------------------|------|-----------|
| Phase 2.6 hardening series | trekexecute.md + headless-launch-template.md | Added `GIT_OPTIONAL_LOCKS`, `--max-budget-usd`, push-before-cleanup, GH#36071 workaround. The launcher is actively maintained and recently hardened — a cap is the next natural hardening. |
| session-decomposer wiring | agents/session-decomposer.md | Established the wave/dependency graph the launcher consumes. Stable; not the edit site. |
| profile system (v4.1) | lib/profiles/ | Introduced `phase_models` + `--profile`; the lookup order a `max_parallel` knob should reuse. |

## Ownership / hot files

- `templates/headless-launch-template.md` is a **hot file** — multiple recent
  hardening commits. Expect a strict doc-consistency needle list; any edit must
  keep all existing needles AND add the new one.
- `commands/trekexecute.md` Phase 2.6 is co-edited with the template in every
  hardening commit ("template mirrors Phase 2.6"). Keep them in lockstep.

## Active branches / risk of conflict

Single active branch (`main`); polyrepo, frequent small commits. Low conflict
risk. The kjøremodus is one-task-per-session, so this change should be a single
focused commit touching resolver + template + prose + tests.

## Signal

The project's own history shows a consistent preference: bound risky externalities
explicitly (budget, locks, turns). An unbounded fan-out is the conspicuous gap in
that pattern — the change is in-character with how this launcher has evolved.