docs: close paragraph-merge repair traceability when archiving OpenSpec

[stevenobiajulu]

Close paragraph-merge repair traceability at archive

After PR#980's post-merge verification, archive the approved repair-paragraph-merge-formatting change in a separate focused docs/test-mapping PR, per repository OpenSpec workflow.

• Record completed full-root, corpus, review and post-merge smoke evidence in tasks.md without falsely claiming pending shipping steps were run at the earlier implementation commit.
• Add the docx-comparison delta to coverage enforcement before canonical promotion; map all five scenarios to real assertions. Numbered Accept/Reject currently share an opt-in actual-reader test; reader/native disagreement is a release gate. Do not attach decorative tags.
• Map the unfiltered Reject ordering AND-clause to the four native/AST parity tests; the tagged primitive scenario currently exercises selective-author history retention.
• Replace stale Step-3-merge comment references in trackChangesAcceptorAst.ts with phase-independent wording.
• Preserve Word-unverified limitations for every matrix row and the separate inherited issues#979,test(docx-core): characterize terminal paragraph-mark cleanup parity #982,test(docx-compare): characterize inherited LibreOffice Reject cross-reference recalculation #983,fix(docx-core): preserve live section and mark properties when rejecting pPrChange #984,test(docx-core): characterize moveTo paragraph-mark Reject parity #985.
• Strictly validate OpenSpec and coverage after archive, then review and ship through normal gates.

No runtime expansion or hosted API work. Final independent Opus approval applies to25ff4870; doc/test mapping follow-up must accurately distinguish that evidence from subsequent changes.