Terramate stack discovery without git repository context

Goal

Use Terramate to discover and orchestrate stacks in environments where a git repository is unavailable or where stack.hcl files are not tracked by git.

Constraints and uncertainty

Terramate's documented stack discovery relies on readable local .git metadata for change detection. The CLI does not describe a fallback mechanism when stack.hcl files are untracked, uncommitted, or when the tool runs outside a git repository. Version-specific CLI flags for stack selection may alter this behavior, but no public documentation constrains the outcome in these scenarios.

Questions

1. What is the expected stack discovery behavior when no .git directory exists in the working tree?
2. Does Terramate provide a configuration option to disable git-based change detection and process all discovered stacks unconditionally?
3. How does stack selection treat untracked or uncommitted stack.hcl files in an otherwise valid git repository?