docs: fix 329 Microsoft.Contractions hits with proper safety checks
Apply contraction fixes across ~40 doc files (setup, integrations, lifecycle, networking, scheduler, swarm, tools, trust-boundary, UI, etc.). Skipped 14 hits: - 10 where words appear in ALL CAPS for deliberate emphasis (is NOT, do NOT, etc.) - 4 where text could not be safely located due to markdown formatting or column position Applied via systematic scan with checks for fenced code blocks, inline code spans, and intentional caps. Preserves sentence-initial capitalization throughout.
This commit is contained in:
iris
mara
parent
77296aff35
commit
78021ce982
38 changed files with 320 additions and 320 deletions
|
|
@ -59,7 +59,7 @@ response, so no redundant loose-end follows. Narrow best-effort race: a
|
|||
actually finishes can still occasionally get both.
|
||||
|
||||
Tasks marked `interrupted` had their process killed by a harness
|
||||
restart; a best-effort todo is still surfaced so the agent is not
|
||||
restart; a best-effort todo is still surfaced so the agent isn't
|
||||
silently blocked.
|
||||
|
||||
Exposed as `mcp__bash__status`.
|
||||
|
|
|
|||
|
|
@ -569,7 +569,7 @@ Merge the PR
|
|||
|
||||
###### **Options:**
|
||||
|
||||
* `--method <METHOD>` — Merge strategy (default: a merge commit). Squash is not offered
|
||||
* `--method <METHOD>` — Merge strategy (default: a merge commit). Squash isn't offered
|
||||
|
||||
Default value: `merge`
|
||||
|
||||
|
|
@ -580,7 +580,7 @@ Merge the PR
|
|||
Rebase the head branch onto the base, then fast-forward
|
||||
|
||||
* `--keep-branch` — Keep the head branch after merging (deleted by default)
|
||||
* `--force` — Merge even if the PR is not mergeable, CI is not green, or a review requests changes
|
||||
* `--force` — Merge even if the PR isn't mergeable, CI isn't green, or a review requests changes
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ list (show/create/edit/status/merge/reviews/commits/diff/view/comment/
|
|||
comments/close/reopen/labels/assign/dependency/reaction/timeline as applicable).
|
||||
|
||||
The flat forms are two different groups, and `--help` hides both, so the
|
||||
difference cannot be seen from the CLI and is stated here instead:
|
||||
difference can't be seen from the CLI and is stated here instead:
|
||||
|
||||
- **Renamed — these no longer run.** `issue-create` `issue-edit` `pr-create`
|
||||
`pr-status` `pr-merge` `pr-reviews` `pr-commits` `pr-assign-reviewer` `diff`
|
||||
|
|
@ -40,7 +40,7 @@ difference cannot be seen from the CLI and is stated here instead:
|
|||
are removed outright in a later release.
|
||||
- **Kind-agnostic — these stay.** `view` `comment` `comments` `close` `assign`
|
||||
`labels` `timeline` are the only way to act on a number without already
|
||||
knowing whether it is an issue or a PR, which no namespaced form offers.
|
||||
knowing whether it's an issue or a PR, which no namespaced form offers.
|
||||
Hidden, but supported; prefer `issue <verb>` / `pr <verb>` when the kind is
|
||||
known, since those validate it.
|
||||
|
||||
|
|
@ -217,7 +217,7 @@ plain comment show under `last comment`, not `reviews`.
|
|||
|
||||
### Repo management
|
||||
|
||||
Agents **cannot create repos directly via forge token** — Forgejo
|
||||
Agents **can't create repos directly via forge token** — Forgejo
|
||||
disables push-to-create and the agent token doesn't have the Create
|
||||
scope. Two paths exist depending on where the repo should live:
|
||||
|
||||
|
|
@ -225,7 +225,7 @@ scope. Two paths exist depending on where the repo should live:
|
|||
MCP tool (requires the `forge` tool group). hive-c0re creates the repo in
|
||||
the c0re-owned `agents/` org, adds you as a write collaborator (not
|
||||
owner), and enables branch protection (operator-team merge approval
|
||||
required — you cannot self-merge). Clone URL is returned immediately.
|
||||
required — you can't self-merge). Clone URL is returned immediately.
|
||||
This is the standard path for agents that need a working repo.
|
||||
|
||||
**Other repos** — Use the CLI verbs below (`repo-create` / `repo-add-collaborator`).
|
||||
|
|
@ -346,7 +346,7 @@ to discover valid label names before triaging or to audit the label set.
|
|||
normal query).
|
||||
- ⚠️ `--assignee` / `--author` are deliberately **not** validated: someone
|
||||
who has left still legitimately appears on old issues, so a login that
|
||||
isn't a current member is not necessarily a typo.
|
||||
isn't a current member isn't necessarily a typo.
|
||||
- `list --limit N` is a *request*: the forge clamps page size to its own
|
||||
`api.MAX_RESPONSE_ITEMS` (50 by default), so `--limit 400` returns at
|
||||
most 50 rows. The stderr trailer reports the real total from the
|
||||
|
|
|
|||
|
|
@ -132,7 +132,7 @@ For an existing agent, persists the token to its state dir; for a human/other ac
|
|||
|
||||
Show + reconcile the divergence between an agent's local applied config checkout and its forge `agent-configs/<agent>` main.
|
||||
|
||||
Always prints the diff first. `--from forge` resets the local checkout to forge main (effective on the next deploy); `--from local` is not supported yet. With no `--from`, prompts for the direction.
|
||||
Always prints the diff first. `--from forge` resets the local checkout to forge main (effective on the next deploy); `--from local` isn't supported yet. With no `--from`, prompts for the direction.
|
||||
|
||||
**Usage:** `hivectl forge reconcile-config [OPTIONS] <AGENT>`
|
||||
|
||||
|
|
@ -406,7 +406,7 @@ Start this EXISTING agent container. Fails immediately if `name` has no config/t
|
|||
|
||||
###### **Options:**
|
||||
|
||||
* `--paused` — Start (or leave) the agent paused: if it's currently down, the pause marker is written before the container boots, so it comes up paused instead of driving turns immediately. If it's already running, this pauses it in place and does not attempt a (re)start
|
||||
* `--paused` — Start (or leave) the agent paused: if it's currently down, the pause marker is written before the container boots, so it comes up paused instead of driving turns immediately. If it's already running, this pauses it in place and doesn't attempt a (re)start
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -50,7 +50,7 @@ hivectl forge reconcile-config iris --verbose # include the full diff, not
|
|||
- `reconcile-config <agent>` shows the divergence between the agent's local
|
||||
applied config checkout and its forge `agent-configs/<agent>` `main`, then
|
||||
reconciles. `--from forge` resets the local checkout to forge `main` (takes
|
||||
effect on the next deploy — it does not auto-rebuild). `--from local` is not
|
||||
effect on the next deploy — it doesn't auto-rebuild). `--from local` isn't
|
||||
supported yet (forge `main` is core-only branch-protected; resolve via a
|
||||
config PR). With no `--from` it prompts for the direction after the diff.
|
||||
|
||||
|
|
@ -126,7 +126,7 @@ hivectl gateway list-users # list all usernames, one pe
|
|||
```
|
||||
|
||||
Passwords are hashed with BCrypt (cost 12) by the daemon. The file is
|
||||
created if it does not exist. Re-running `create-user` with the same
|
||||
created if it doesn't exist. Re-running `create-user` with the same
|
||||
username updates the password hash in place.
|
||||
|
||||
## Agents
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
Two tool groups govern agent lifecycle management and config changes.
|
||||
Both are scoped to **direct children only** (topology-enforced: the
|
||||
server rejects any name that is not a direct child of the calling
|
||||
server rejects any name that's not a direct child of the calling
|
||||
agent per `topology.json`). Privileged agents (e.g. ruth) may operate
|
||||
on any sub-agent — the topology scope applies to all others.
|
||||
|
||||
|
|
|
|||
|
|
@ -66,7 +66,7 @@ the machine name (`h-<name>`). `lines` defaults to 50, host-capped at 500.
|
|||
## `read_host_journal` capability
|
||||
|
||||
Capability-gated (not a tool group) — the operator enables it in the
|
||||
P3RM1SS10NS C4P4B1L1T13S section. Unlike tool groups this is not
|
||||
P3RM1SS10NS C4P4B1L1T13S section. Unlike tool groups this isn't
|
||||
configurable from `agent.nix`.
|
||||
|
||||
### `get_host_journal(unit?, container?, lines?, priority?, grep?, since?, until?)`
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ swarm-level operator CLI
|
|||
* `--authelia-bin <PATH>` — authelia binary used to hash passwords. The argon2 parameters must match the verifier's, so this has to be the *configured* package rather than whatever is on `PATH`
|
||||
* `--users-file <PATH>` — Host-side path of authelia's users database — i.e. the path inside the container, prefixed with the container's root.
|
||||
|
||||
This is the only user store: it is read before every change and written in place, and `swarm-authelia-bridge` writes the same file.
|
||||
This is the only user store: it's read before every change and written in place, and `swarm-authelia-bridge` writes the same file.
|
||||
|
||||
|
||||
|
||||
|
|
@ -53,7 +53,7 @@ Add a user, generating a password for them
|
|||
|
||||
###### **Arguments:**
|
||||
|
||||
* `<USERNAME>` — Login name. Conservative ASCII only — it is a YAML map key and reaches access-control rules and logs
|
||||
* `<USERNAME>` — Login name. Conservative ASCII only — it's a YAML map key and reaches access-control rules and logs
|
||||
|
||||
###### **Options:**
|
||||
|
||||
|
|
@ -79,8 +79,8 @@ Every flag is optional and they compose, so one call can set several things at o
|
|||
|
||||
* `--display-name <TEXT>` — Name shown in the SSO UI
|
||||
* `--email <ADDRESS>`
|
||||
* `--add-group <GROUP>` — Repeatable. Adding a group the user is already in is not an error
|
||||
* `--remove-group <GROUP>` — Repeatable. Fails if the user is not in the group — a revocation that reports success without revoking is the failure nobody re-checks
|
||||
* `--add-group <GROUP>` — Repeatable. Adding a group the user is already in isn't an error
|
||||
* `--remove-group <GROUP>` — Repeatable. Fails if the user isn't in the group — a revocation that reports success without revoking is the failure nobody re-checks
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue