Joseph Doherty
6ba52a68f0
0.6.0 moves the store-path rules into the shared library — both the rooted check and the content-root check — with a SecretsOptionsValidator wired into AddZbSecrets and validated on start, so all four consuming apps get the guard from one implementation rather than four copies. mxgw therefore adds no local validator over the Secrets section. This is a four-minor jump, not a re-pin: mxgw was on 0.2.3 and skips 0.3.0, 0.4.0, 0.4.1, 0.5.0 and 0.5.1 in one step. Verified rather than assumed — diffing the 0.2.3 and 0.6.0 assemblies shows the added surface is the new path rules and their plumbing (AddIfNotRooted, AddIfUnderContentRoot, ComputeDefaultSqlitePath, DefaultSqlitePath, IValidateOptions, IsPathRooted, GetFullPath) and nothing touching store or delete behaviour. Secrets.Ui is byte-identical across the range: both assemblies are 39424 bytes and differ only in the version stamp, because this package family shares one version across every package even when a release touches only one of them. So the browser gate run against the /admin/secrets delete modal on 0.2.3 still covers what ships here. The library default is LocalApplicationData-derived so the family's cross-platform apps still boot locally. The gateway keeps its own CommonApplicationData value, which always wins — see the note on ApplyDefaultSecretsStorePath for why the difference is deliberate and why deleting that method as a redundancy would silently move the store.