Align bottleneck validity at gauges Ensuring the validity of a bottleneck version is always contained by the validity of the referenced gauge version allows to reliably determine matching reference values of the gauge at a point in time. Since this implies that a bottleneck version might be cut into more than one time ranges, the concept of having only one non-erased version is no longer applicable and replaced by using the 'current' version of a bottleneck. Fairway availability data are always kept with the 'current' bottleneck version to have them at hand alltogether for analyses over longer time ranges.

# documentation
**/README*
**/docs
**/*.md

# backend binary
cmd/gemma/gemma

# Dependency directories
**/node_modules

# local dotenv environment variables file
client/.env.local

# Tags tables
**/TAGS