Fix initial-policy test and docs after gate rename

Co-authored-by: Honor <e0bf479eeebe47dde1e35705212a4df70616a7bc834d907ddfb18cf0405f8b1b@seiler-test.communities.public.builderlabstaging.xyz>
Signed-off-by: Brad Seiler <seiler@squareup.com>
This commit is contained in:
Brad Seiler
2026-11-06 15:32:57 -05:00
parent c0329d36dc
commit d31793ccbc
2 changed files with 2 additions and 2 deletions

View File

@@ -34,7 +34,7 @@ mod postgres_tests {
.unwrap();
let owners: Vec<_> = (0..4).map(|_| Keys::generate()).collect();
let owner = &owners[3];
assert!(!state.config.nip_fi_upgrades_enabled);
assert!(!state.config.nip_fi_changes);
for (index, policy) in [
None,
Some(Value::Null),

View File

@@ -87,7 +87,7 @@ an operator disable or a change in issuer configuration. A different owner
retains the existing conflict. Legacy ensure and deployment bootstrap remain
optional and do not accept an explicit initial policy.
This policy is independent of `BUZZ_NIP_FI_UPGRADES_ENABLED`. Mode `off` stores
This policy is independent of `BUZZ_NIP_FI_CHANGES`. Mode `off` stores
it but bypasses enforcement. The production creation paths are operator
create-only, legacy operator ensure, and deployment bootstrap; only create-only
accepts this choice.