feat: rename to paperspec and add the website

- Rename manuspec to paperspec everywhere outside pixi.toml: prose, the
  tools, provenance tool names and the fixture key derivations, so every
  fixture and vector is rebuilt.
- Move the namespace addresses under the site, mirroring the repository:
  schema $id https://paperspec.scient.ing/schemas/<file>, the JSON-LD
  context https://paperspec.scient.ing/context/scienting-1.jsonld, and
  term IRIs https://paperspec.scient.ing/vocab#<term>. Format
  identifiers (scienting-*) and URNs (urn:scienting:) are unchanged.
- tools/site.py (standard library only) builds _site/: every file of the
  repository at its own path, each Markdown file rendered as a page with
  sidebar navigation, heading anchors matching the forge's, folder
  listings, a vocabulary page for the context's IRIs, a heading search
  and a 404 page; light and dark themes.
- check.py builds the site and checks that every Markdown file has a
  page, every internal link and fragment resolves, no Markdown is left
  unrendered, and every $id, the context address and the vocabulary IRIs
  are files of the site.
- deploy/: a Caddyfile with the media types and CORS the data needs, and
  a guide; .gitea/workflows/site.yml builds on main and publishes with
  rsync when the SITE_* secrets are set.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/faq.md

@@ -1,9 +1,9 @@
 # FAQ
 
-This page answers questions about manuspec, a set of file formats that give every sentence and table cell of a scientific paper a permanent address.
+This page answers questions about paperspec, a set of file formats that give every sentence and table cell of a scientific paper a permanent address.
 Newcomers, implementers of a reader, writer, converter or checker, and experts who know JATS (Journal Article Tag Suite), TEI (Text Encoding Initiative) or W3C Web Annotations can all use it.
 Each answer gives the plain statement first, then the precise one, then the chapter that defines it.
-The repository is <https://git.scient.ing/infra/manuspec>, and the formats are at version 0.1.0.
+The repository is <https://git.scient.ing/infra/paperspec>, and the formats are at version 0.1.0.
 
 ## Can I read these files without special software?
 
@@ -82,13 +82,13 @@ Whether a team may share notes on a paper this way is a question for its own cou
 
 They overlap in subject, not in job.
 
-JATS, the [Journal Article Tag Suite](https://www.niso.org/publications/z3996-2024-jats) (ANSI/NISO Z39.96-2024), is an XML format for publishers and archives to exchange journal content. manuspec does not replace it.
+JATS, the [Journal Article Tag Suite](https://www.niso.org/publications/z3996-2024-jats) (ANSI/NISO Z39.96-2024), is an XML format for publishers and archives to exchange journal content. paperspec does not replace it.
 A JATS file is one kind of witness (a source file), an input from which a document is established.
 None of the 312 elements in the [JATS 1.4 Archiving tag library](https://jats.nlm.nih.gov/archiving/tag-library/1.4/) marks a sentence; its smallest text unit is the paragraph, `<p>`.
 
 TEI, the Text Encoding Initiative, has a sentence-like [`<s>` element](https://tei-c.org/release/doc/tei-p5-doc/en/html/ref-s.html) and keeps both readings of a corrected passage with [`<corr>` and `<sic>`](https://tei-c.org/release/doc/tei-p5-doc/en/html/ref-corr.html).
 The encoder assigns its `xml:id`, and the guidelines [recommend it for durability](https://tei-c.org/release/doc/tei-p5-doc/en/html/SA.html).
-manuspec mints and retires IDs by rule, keeps corrections as separate records with evidence, and hashes each node.
+paperspec mints and retires IDs by rule, keeps corrections as separate records with evidence, and hashes each node.
 
 Keep JATS for publisher and archive exchange and TEI for general scholarly text encoding.
 A TEI file is a witness of kind `xml` ([spec/02 §2.3](../spec/02-model.md)).