[morningman]

Summary

The Russian planner keeps reopening four deletion tasks from its fixed T03 inventory after the Binlog-to-Changelog renames in #4426. Record the reviewed deletions so subsequent plans stop requesting cleanup that is already complete.

The ledger binds each task to its original ID, source path and source hash, with a timestamp, explicit machine-review identity and evidence from #4426/#4431. At Apache master a0312e41f13f47ff7da7855759d0d6f7ed3b5fc1, all four replacement Russian documents are current, obsolete sources/targets/state records are absent, affected inbound links and sidebars are clean, and the actual Docusaurus createRedirects callback maps all four old Russian URLs to their replacements. The remaining references to the old image filename point to an existing retained asset.

Validation

• Existing planner tests: 19 passed, including reviewed-deletion suppression and evidence validation.
• Configuration checks pass for all three managed locales; the four ledger records pass validateResolved.
• Native audit and planner comparison: deletion tasks drop from 4 to 0. Coverage and all six unrelated source-update tasks remain unchanged: required/current/pending = 3354/3348/6; no sidebar gaps or planner exceptions.
• Shared Russian PR preflight and git diff --check pass. No document bodies or page-state records change, so preflight checks zero changed documents.
• All four Russian redirect mappings verified through the loaded Docusaurus configuration. No website build or public deployment was performed locally; CI selects Russian 4.x.

The six remaining Russian 4.x tasks come from the later source changes in #4441: four new distance-function documents and updates to Lance Catalog and hybrid search. This ledger change preserves those tasks and does not claim complete current coverage.

Self-review

Checkpoint	Conclusion
Goal	Four completed historical cleanup tasks disappear from planning while new source work remains visible.
Scope and clarity	One locale-specific ledger file; original inventory and translation identities are preserved.
Information architecture	Current docs, active versions, community pages and other locales retain their existing content and navigation.
Paths, links and redirects	No paths or anchors change here; all four existing replacement routes, cleanup and redirects were checked.
Frontend and build conventions	No frontend, style, theme, workflow or build changes. Responsive/theme behavior is unaffected.
Verification	Native audit/planner comparison, existing planner tests, configuration/schema validation, actual redirect callback and shared admission checks cover the metadata change. CI/public deployment results are not asserted.
Other correctness, accessibility, SEO and maintenance	No additional issue found in this change. Ledger evidence and machine identity remain explicit; six new source-update tasks are reported separately.

Versions

• dev
• 4.x
• 3.x
• 2.1 or older (not covered by version/language sync gate)

Languages

• Chinese
• English
• Russian translation-state ledger

Docs Checklist

• Checked by AI
• Test Cases Built (metadata-only change; existing tests and native checks run, no new tests or website build)
• Updated required version and language counterparts, or explained why not
• If only one language changed, confirmed whether source/translation counterparts need sync

The ledger belongs only to Russian. The existing English/Chinese sources, Russian replacement documents and shared redirects are already merged and need no counterpart edits for this bookkeeping change.