matrix, docs: drop the last admin framing, fix tense and prose lint
Three leftovers from the rename, plus the gating prose job.
`nix/packages/default.nix` still described the minter as the "matrix
admin credential's minter", and shipped that claim in the package's
`meta.description` — a PR-visible string.
`promote_user_to_admin`'s doc comment pointed at the `admin_execute`
entry in `hive-matrix.nix` as the thing that bootstraps the first
admin. That entry is gone, so the comment referenced nothing. It now
records that the account is ordinary, that the call therefore has no
working sender, and that rehoming at swarm level is the fix rather than
re-granting. `reset_user_password` gained the matching warning; it had
none.
The prose fixes clear all 8 `CI / prose lint (vale, errors)` failures,
all of which were in docs this branch touches. No vale config change,
no exception, no carve-out: contractions, one recast sentence, one
de-hyphenation and one dropped "simply".
Tense: four docs described system behaviour in the future ("will
refuse", "will fetch and trust"). Reference docs get read from the
other side of the change, so they say what the system does.
This commit is contained in:
parent
88b4a7841d
commit
bbb4e471ea
5 changed files with 27 additions and 19 deletions
|
|
@ -181,7 +181,7 @@ which. A hive that does **not** deploy the store names the reader's three
|
|||
itself: the operator issues that leaf out of band, and it's the one credential
|
||||
the store can't hand you, being what opens it. ⚠️ Not the gateway's HTTPS certificates and not the hive CA — this is
|
||||
**mTLS between services and the store**, a separate trust domain, because a
|
||||
store that took its identity from an authority it will itself distribute could
|
||||
store that took its identity from an authority it itself distributes could
|
||||
never come up before that authority.
|
||||
|
||||
### 4 · Swarm SSO (only when `deploy.authelia`)
|
||||
|
|
@ -203,8 +203,8 @@ surfaces (the swarm UI below) gate on that group, and an account
|
|||
without it authenticates successfully and is then refused — which reads
|
||||
like a broken login rather than a missing group.
|
||||
|
||||
If an account already exists without it, `user add` will refuse rather
|
||||
than amend — adding the group afterwards is `swarmctl user update mara
|
||||
If an account already exists without it, `user add` refuses rather
|
||||
than amends — adding the group afterwards is `swarmctl user update mara
|
||||
--add-group admins`.
|
||||
|
||||
Detail, including what the password is and why this stays manual:
|
||||
|
|
|
|||
Loading…
Reference in a new issue