dm-bip seven-bridges submit accepts --profile in both execution modes, but only single-consent acts on it. The cohort branch calls _submit_cohort_mode(...) without passing profile, so Profile never reaches the task body — submit --cohort-mode --profile runs with no diagnostics and reports nothing unusual.
The fix depends on a decision that hasn't been made yet, which is why this is worth writing down rather than patching straight away.
No cohort-mode app exists on any tier except test. dmc-harmonization-multiconsent-app is the only one, and it declares no Profile input. So even if the CLI forwarded the flag, there is currently nowhere for it to land.
That leaves two coherent answers:
- If a dev-tier cohort app gets created — which is the natural place to exercise and profile cohort mode, given diagnostics belong on dev — then forward
profile through _submit_cohort_mode and have that app declare a Profile input, matching cc-dm-bip-test.
- If cohort mode stays test-and-prod only, reject the combination outright.
submit --cohort-mode --profile should fail with a message saying profiling is single-consent only, rather than accepting a flag nothing can act on.
Either is fine; silently accepting it is not. This is the same failure shape as #362 — an input accepted where nothing downstream can honor it — except here the CLI is the one dropping it rather than the app.
Documented as current behavior in RELEASING.md (#364).
dm-bip seven-bridges submitaccepts--profilein both execution modes, but only single-consent acts on it. The cohort branch calls_submit_cohort_mode(...)without passingprofile, soProfilenever reaches the task body —submit --cohort-mode --profileruns with no diagnostics and reports nothing unusual.The fix depends on a decision that hasn't been made yet, which is why this is worth writing down rather than patching straight away.
No cohort-mode app exists on any tier except test.
dmc-harmonization-multiconsent-appis the only one, and it declares noProfileinput. So even if the CLI forwarded the flag, there is currently nowhere for it to land.That leaves two coherent answers:
profilethrough_submit_cohort_modeand have that app declare aProfileinput, matchingcc-dm-bip-test.submit --cohort-mode --profileshould fail with a message saying profiling is single-consent only, rather than accepting a flag nothing can act on.Either is fine; silently accepting it is not. This is the same failure shape as #362 — an input accepted where nothing downstream can honor it — except here the CLI is the one dropping it rather than the app.
Documented as current behavior in RELEASING.md (#364).