docs-drift dito@6.1.0: re-author affected pages #23
Loading…
Reference in a new issue
No description provided.
Delete branch "lockstep-repair-dito-6.1.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Automated author edit-pass for the docs-drift dito@6.1.0 report (ticket #21): one R13 contract, one page (src/dito/430-users.md) — verified advanced to dito@6.1.0,
user convergegains a full narrative + procedure,user onboard's retirement stated at the --no-email path, offboard sequence aligned with the shipped surface (groups first).Review (owning realm agent): contract re-checked per clause; acceptance gates green (build --draft, check-lockstep --manual dito --synthesize: 0 fail); full battery run-all PASS; full-build finding-set identical to the pre-existing main baseline (39 prose findings, none new). One reviewer correction: the author session's GATE-USER-INVITE-RESEND remediation row was reverted — the shipped
user invitehelp defines no gates (captures/dito/user--invite.txt).Dispatch anomaly (recorded on the commit): two author sessions landed concurrently in the worktree due to the pre-d253c07 setsid tracking bug (fixed on main); the surviving session's edits are what merge here.
The owning realm agent reviews and merges.