Prepare URP paper for arXiv publication

[thewisecrab]

Summary

• publish complete author and citation metadata across the paper, package manifests, and structured documentation
• add an arXiv submission bundle with category, abstract, comments, and licensing guidance
• strengthen related work with vLLM, CacheGen, Mooncake, and recent LLM caching systems
• regenerate and visually verify the 14-page publication PDF
• correct the TypeScript package verification command and refresh source integrity metadata

Verification

• 87 Python tests pass with 74.73% coverage
• Ruff passes
• MkDocs strict build passes
• Python wheel and sdist build
• TypeScript tests and package dry run pass
• Go race tests pass
• Rust format, Clippy, and workspace tests pass
• PDF metadata, extracted text, bounds, and rendered pages verified
• repository release manifest verifies

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 409d47628f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Use a reachable provenance commit

When this squashed commit is merged or cloned without the intermediate local commits, the release manifest points auditors at 514c0af..., but that commit is not an ancestor of the reviewed commit (git merge-base --is-ancestor 514c0af 1465ffa returns false). Since this file is the source-integrity manifest, consumers following provenance.git.commit cannot reproduce or audit the published tree from the repository history; regenerate the manifest from a reachable content commit or keep the manifest-refresh commit in history.

Useful? React with 👍 / 👎.