@ricsam/r5d-worker 0.0.58 → 0.0.60

package/README.md

@@ -17,7 +17,7 @@ Web shells and agent shell commands receive a server-issued `r5dctl` credential
 
 When the user has signed in with GitHub, web shells and agent commands also receive that OAuth credential through `GH_TOKEN`. GitHub CLI commands such as `gh pr`, `gh issue`, and `gh workflow` therefore use the signed-in user's permissions without a separate `gh auth login` on the worker host. Signing in again refreshes the granted OAuth scopes for subsequently started commands and shells.
 
-Visible branch checkouts are the user/agent workbench. Their `origin` remains the connected GitHub repository for manual Git work. r5d internal sync git metadata lives separately under `~/.r5d/sync`; each worker periodically snapshots eligible working-tree changes and reconciles them with the canonical workspace like an independent Git client. Ordinary commands and shells may remain active while this happens. Compatible inbound changes are hydrated into the visible checkout, while paths changed locally since the snapshot are preserved for a later sync or conflict-remediation pass. Canonical remediation shells are the exception: they edit the hidden synchronization checkout directly and remain serialized with synchronization.
+Visible branch checkouts are the user/agent workbench. Their `origin` is the authenticated r5d canonical project repository; GitHub remains available separately through `gh` and the injected OAuth credential. r5d workspace metadata lives under `~/.r5d/sync`, and each worker behaves like an eventually consistent Git client. Known writes advance a durable dirty generation and coalesce into a publication after five quiet seconds or at a process/agent boundary. Publications run while ordinary shells and commands remain active: the worker rejects unstable snapshots and hydrates only paths that still match their captured preimages. The worker uploads an immutable candidate, while the server alone promotes canonical `main` with compare-and-swap. A 60-second scan catches missed notifications and out-of-band edits. Canonical remediation shells are the exception because they edit the hidden synchronization checkout directly and remain serialized with exact synchronization.
 
 Branch names managed by r5d use lowercase letters, numbers, internal hyphens, and slash-separated segments, for example `ft/esm-support`. They may contain at most 45 characters. On the first start after upgrading to the nested checkout layout, the worker atomically moves each unambiguous legacy `<namespace>-<project>` directory to `<namespace>/<project>`. If both paths exist, it preserves both and stops with recovery instructions.