Make technical paper arXiv-ready

[thewisecrab]

What changed

• restructure the URP manuscript as a neutral systems technical paper with explicit contributions, methodology, results, related work, limitations, references, affiliation, and AI-tool disclosure
• generate an arXiv-ready PDF with embedded TrueType fonts, machine-readable text, distinct CC BY 4.0 article and Apache-2.0 software licensing, deterministic output, and synchronized metadata
• add a canonical arXiv submission bundle, automated verifier, compliance record, CI artifact, and release-manifest evidence
• align README, documentation navigation, llms.txt, and TechArticle JSON-LD with the revised paper and license

Why

The previous PDF used unembedded standard fonts, mixed article and software licensing, lacked an explicit affiliation and generative-AI disclosure, and read more like a promotional white paper than a refereeable systems submission. These changes make the repository enforce current arXiv upload and metadata requirements instead of relying on a manual checklist.

Validation

• 87 Python tests pass; coverage gate passes at 74.73%
• TypeScript tests and build pass
• Go race tests pass
• Rust fmt, clippy, and 8 tests pass
• MkDocs strict build and TechArticle JSON-LD validation pass
• local production-readiness and all platform contract checks pass
• arXiv verifier passes: 16 A4 pages, 1 figure, 1,455-character ASCII abstract, embedded TrueType fonts, no encryption, JavaScript, attachments, or multimedia
• PDF rebuild is byte-reproducible at SHA-256 3d543f9d8911119a4953f779c7fe1ac70b2440f2f5a01dd71336aa5027c18c8c
• release manifest verifies all 259 active distribution files