Bind Wiki publication checks to the exact source tree and pushed commit

[Infiland]

Follow-up to #712 and PR #851.

Problem

The documented Wiki publication process inspects staged Markdown changes and later checks only that git ls-remote ... HEAD succeeds. Those checks do not conclusively prove that the complete live Wiki tree equals the reviewed docs/wiki/ tree, or that remote HEAD, the default branch, a fresh clone, and the issue-closing evidence all refer to the exact Wiki commit that was pushed.

An unchanged extra page or alternate-markup file can escape a staged-diff check. A concurrent post-push edit can also make otherwise valid verification evidence stale.

Scope

• Pin and record the merged source commit and exact docs/wiki tree ID.
• Require the staged Wiki tree from git write-tree to equal the canonical source tree before committing.
• Record the Wiki default branch, pre-publication commit, and published commit.
• Require the publication commit to have the recorded parent and canonical tree.
• Bind remote HEAD and the explicit default branch to the published commit immediately after push and again before recording completion.
• Require a fresh explicit-branch clone to be clean and match the exact published commit and canonical tree.
• Synchronize the concise and detailed Wiki-maintenance documentation.
• Preserve normal non-force, concurrent-update-safe publication.

Acceptance criteria

• The checklist rejects unchanged extra files, alternate-markup pages, symlinks, and mode/content drift anywhere in the Wiki root.
• The checklist requires exact equality with the merged docs/wiki Git tree ID.
• Remote HEAD, the named default branch, the fresh clone, and recorded evidence are all required to resolve to the exact pushed Wiki commit.
• A concurrent branch movement causes verification to stop and reconcile instead of closing documentation work against stale evidence.
• The source SHA, source tree, Wiki branch, pre-publication Wiki SHA, and published Wiki SHA are all recorded.
• docs/WIKI_MAINTENANCE.md and docs/wiki/Maintainer-Release-and-Wiki.md remain consistent.

This is documentation/process hardening; it does not change converter or generated-runtime behavior.