You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Status.hoist_failure.md on lecture-python.zh-cn is behind: its state records source-sha: dd9fd019 against a source last-touch of a7aafd5b (this PR).
Route.translate forward -f hoist_failure.md from a source clone pulled to origin/main. forward reads the source off the local filesystem, so it cannot exhibit #276's stale-snapshot defect, and it anchors its parity check to current main rather than to the merge-time snapshot.
Two notes. This issue is the one case in the estate whose error is not a structural-parity failure — it reads Update mode requires oldEnglish, newEnglish, and currentTranslation, which looks transient rather than deterministic, so forward has a fair chance of simply succeeding. And under the ruling's precondition this PR is one of only three in the backlog that would have been safe to resync anyway: git rev-list --count a7aafd5b..origin/main -- lectures/hoist_failure.md is 0.
Caveat before running: the target's state file dates from a 2025-era bootstrap, so verify what forward proposes rather than merging on the verdict alone.
This was the one failure in the estate's backlog whose error was not a structural parity check — it read Update mode requires oldEnglish, newEnglish, and currentTranslation, which looked transient, and it was: forward succeeded on the second attempt.
Verified: 46/46 directives, 23/23 code cells, 52/52 headings, 0 python syntax errors across all 23 cells, no captions or axis labels byte-identical to source, and the edition's i18n font block preserved through the whole-file regeneration.
Activity
mmcky commentedon Aug 20, 2026
Route corrected — use the CLI, not
\translate-resyncPer the 2026-08-20 ruling on action-translation#276,
\translate-resyncis no longer the documented recovery for a failed sync.Status.
hoist_failure.mdon lecture-python.zh-cn is behind: its state recordssource-sha: dd9fd019against a source last-touch ofa7aafd5b(this PR).Route.
translate forward -f hoist_failure.mdfrom a source clone pulled toorigin/main.forwardreads the source off the local filesystem, so it cannot exhibit #276's stale-snapshot defect, and it anchors its parity check to current main rather than to the merge-time snapshot.Two notes. This issue is the one case in the estate whose error is not a structural-parity failure — it reads
Update mode requires oldEnglish, newEnglish, and currentTranslation, which looks transient rather than deterministic, soforwardhas a fair chance of simply succeeding. And under the ruling's precondition this PR is one of only three in the backlog that would have been safe to resync anyway:git rev-list --count a7aafd5b..origin/main -- lectures/hoist_failure.mdis 0.Caveat before running: the target's state file dates from a 2025-era bootstrap, so verify what
forwardproposes rather than merging on the verdict alone.mmcky commentedon Aug 20, 2026
Recovered and closing.
hoist_failure.mdis resynced to sourcea7aafd5bonlecture-python.zh-cn@mainas of zh-cn#260 (merged 2026-08-20).Delivered with
translate forward -fat engine v0.26.0, not\translate-resync, per the ruling on action-translation#276.This was the one failure in the estate's backlog whose error was not a structural parity check — it read
Update mode requires oldEnglish, newEnglish, and currentTranslation, which looked transient, and it was:forwardsucceeded on the second attempt.Verified: 46/46 directives, 23/23 code cells, 52/52 headings, 0 python syntax errors across all 23 cells, no captions or axis labels byte-identical to source, and the edition's i18n font block preserved through the whole-file regeneration.