Towergit repeatable environment: unclear OS‑specific permission handling

Goal: configure towergit to produce identical development environments on Linux, macOS, and Windows CI agents so that builds are deterministic.

Uncertainty: the documentation does not specify how towergit reconciles file‑system permissions, environment‑variable scopes, or temporary‑directory locations across these platforms, leaving a gap in the repeatability guarantee.

Questions: Which permission model does towergit apply by default? How can users override or inspect the effective permission settings for each OS? Are there documented limits to what towergit can normalize in a CI pipeline?