Does Bower's flat resolver require manual resolutions for every transitive version conflict?

Bower installs all dependencies into a single flat bower_components directory, allowing only one version of any package per project. When two direct dependencies declare incompatible semver ranges for the same transitive package, the client-side resolver cannot automatically satisfy both. The documented remedy is to add a resolutions object to bower.json to pin the shared package to a specific version. However, it remains unclear whether the resolver has any deterministic fallback behavior when resolutions is absent or incomplete, or whether it reliably fails before writing partial files to disk. Because Bower is deprecated and no longer actively maintained, exact failure semantics may differ across registry endpoints and Git sources; this question assumes the final stable 1.8.x line.

Does the flat resolver always abort with an explicit conflict message when no compatible single version exists, or can it silently install one branch and leave the other dependency unmet? Which bower.json fields—such as resolutions, ignore, or dependencies overrides—are guaranteed to influence the final version mapping before installation begins? When a conflict is resolved manually, does Bower re-evaluate the entire dependency graph on the next install, or does it cache the previous resolution locally?