11: PATH as code, not an HTML em

Cosmetic follow-up to the CB-542 docs merge: the merged text mixed an HTML <em>
into a Markdown sentence that uses * markers either side of it, for a variable
name that should be code in the first place.
Dai Ha
2026-08-13 15:32:33 +02:00
parent 6ff70e187f
commit 8c63db5da6
+1 -1
@@ -147,7 +147,7 @@ toolchain entirely, leaving workers unable to run `mvn` or `java` at all.
the `SubscriptionGuard`. A `subscription: true` profile is the exception: it skips the guard and
injects neither key, so an `ANTHROPIC_BASE_URL`/`ANTHROPIC_AUTH_TOKEN` in its `env:` would survive
unguarded — that configuration is refused at load (see [Run a worker on the subscription](#run-a-worker-on-the-subscription)).
Since the default <em>PATH</em> is the *daemon's* own, start the daemon with a good one (see the
Since the default `PATH` is the *daemon's* own, start the daemon with a good one (see the
`PATH` lines in `deploy/dev.ltms.bridged.plist` and `deploy/bridged.service`).
## Isolated worktree per worker