fix(post-#1635 round-3): §33 compact labels within first 20 lines + Non-fusion disclaimer Qubic-Monero correction

[AceHack]

Round-3 §33 cleanup. Reviewer correctly flagged that even with literal line-start tokens (round-2 fix in #1639), the labels were spread across lines 18-28 with blank lines between them — putting Operational status (line 22) and Non-fusion disclaimer (line 28) OUTSIDE the §33 first-20-lines window.

Fix: compacted by removing blank line between YAML close and labels + condensing each label to one line. All 4 labels now within first 20 lines (lines 17-20).

Plus updated Non-fusion disclaimer wording to fold the Qubic-Monero correction note INTO the disclaimer (was previously a separate Note paragraph that contradicted the disclaimer's still-stale 'antifragile attacks-beneficial' substrate-grade-landings list).

Per wonder-not-reverence-on-yourself-too: format-converging round 3, NOT new substrate. The §33 + numeric format-spec is now satisfied strictly.

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR tightens the GOVERNANCE §33 “archive header” block in a docs/research/** preservation doc by compacting the four required labels so they all fall within the first 20 lines, and by merging the Qubic–Monero correction note into the Non-fusion disclaimer text.

Changes:

• Compacted the §33 header label block (removed blank spacing and made each label single-line) so Scope/Attribution/Operational status/Non-fusion disclaimer are on lines 17–20.
• Updated the Non-fusion disclaimer wording to include the post-merge Qubic–Monero correction reference (PR #1638) and its linked research doc.