pub const KEY: &str = "amont.trusted";Expand description
Where the decision is recorded. Local, never committed — a repository must not be able to declare itself trusted.
MULTI-VALUED, and that is the whole point. --local config is shared by every
worktree of a repository, so a single value meant worktrees fought over it:
trusting one checkout made every other checkout on a different branch report
TRUSTED ONCE, AND CHANGED SINCE, and its declared checks stop running until
somebody re-trusts — which then breaks the first one. With one worktree per
task, as git worktree workflows have, the record never settles.
A set fixes it without moving the record anywhere, because trust here has always been keyed on CONTENT rather than on place: the question is “have these exact bytes been reviewed”, and the answer does not depend on which checkout is asking. Two worktrees with the same amont.conf need one acceptance between them; two with different manifests hold one entry each.
The cost, stated plainly: reverting a manifest to bytes accepted earlier no
longer asks again, where a single-valued record would have. That is the
definition working as written — those bytes WERE reviewed — but it is a
weaker guarantee than before, and [KEEP] bounds how far back it reaches.
--worktree config was the other candidate. It needs
extensions.worktreeConfig=true on the repository, which is amont writing a
repo-wide git setting other tools also read, to fix a problem of its own.