The config the guard actually runs with: the configured slice, or a copy
with the blendable cap replaced by a valid ?densityCap=N override. The
non-blendable cap is documented as the TIGHTER of the two ("one element per
pixel already saturates a max projection"), so an override below it pulls it
down too; an override above it leaves it alone.
The config the guard actually runs with: the configured slice, or a copy with the blendable cap replaced by a valid
?densityCap=Noverride. The non-blendable cap is documented as the TIGHTER of the two ("one element per pixel already saturates a max projection"), so an override below it pulls it down too; an override above it leaves it alone.