@wxxb789/anc 0.0.1

package/src/pages/notes/[slug].astro

@@ -0,0 +1,509 @@
+---
+/**
+ * The note page: requirements section 9.2's thirteen-element anatomy.
+ *
+ * Elements 1, 2, and part of 13 come from `Layout.astro` — the skip link, the
+ * header with its search trigger, and the printed canonical route. Everything
+ * else is here, in the order the requirements list them, and every region is
+ * either rendered below or left as a named, empty slot with the ticket that
+ * owns it. **Do not fill a slot from another ticket**: the slot is the contract.
+ *
+ * | § 9.2 element | Where |
+ * | --- | --- |
+ * | 1 skip link | `Layout.astro` |
+ * | 2 header and search trigger | `Layout.astro` |
+ * | 3 breadcrumbs | here |
+ * | 4 title and public metadata | here |
+ * | 5 optional summary | here |
+ * | 6 table of contents | here, via `TableOfContents.astro` |
+ * | 7 sanitized article content | here |
+ * | 8 outgoing public links | here |
+ * | 9 static backlinks | here |
+ * | 10 related-note fallback | here, derived by `relations.ts` |
+ * | 11 local-graph island | here, via `NoteGraph.astro`, laid out by `graph.ts` |
+ * | 12 previous/next or collection navigation | here |
+ * | 13 footer with provenance and canonical URL | here; the absolute URL is TK-08 |
+ *
+ * Reading and navigation need no JavaScript. The table of contents is server
+ * rendered, the breadcrumbs are static, and code-copy is a progressive control
+ * inserted only when scripting runs.
+ */
+import Layout from '../../layouts/Layout.astro';
+import LinkedNotes from '../../components/LinkedNotes.astro';
+import NoteGraph from '../../components/NoteGraph.astro';
+import TableOfContents from '../../components/TableOfContents.astro';
+import { entries, getEntry, tagFacets, tagRouteForLabel } from '../../lib/content.js';
+import { hasDrawableGraph, localGraph } from '../../lib/graph.js';
+import { renderMarkdown } from '../../lib/markdown.js';
+import {
+  collectionNeighbours,
+  hasTagPeer,
+  notesForSlugs,
+  relatedNotes,
+} from '../../lib/relations.js';
+import { GRAPH_SEGMENT, collectionRoute, noteRoute } from '../../lib/routes.js';
+import { canonicalUrl, TITLE_SUFFIX } from '../../lib/site.js';
+import { translate, NAV_LANGUAGE, partLanguage } from '../../lib/translations.js';
+// Loaded as a URL rather than imported, so the stylesheet becomes its own
+// content-hashed asset and the `<link>` below can be emitted conditionally.
+// Importing it would merge it into the layout's sheet and ship it everywhere,
+// which is precisely what owner decision 7 rules out.
+import codeStylesheet from '../../styles/code.css?url';
+import mathStylesheet from '../../styles/math.css?url';
+import diagramStylesheet from '../../styles/diagram.css?url';
+import graphStylesheet from '../../styles/graph.css?url';
+import { DIAGRAM_MODE } from '../../lib/diagram-mode.js';
+import { MATH_MODE } from '../../lib/math-mode.js';
+
+export function getStaticPaths() {
+  return entries.map((entry) => ({ params: { slug: entry.slug }, props: { entry } }));
+}
+
+const { entry } = Astro.props;
+
+/**
+ * **The one route that is a document**, and therefore the whole point of TK-16.
+ *
+ * Every other page on this site aggregates many entries or none and resolves its
+ * chrome from the navigation language. This one renders exactly one artifact
+ * entry, so it resolves from that entry's own `language` — and the result is
+ * that a zh-CN note renders Chinese chrome under `<html lang="zh-CN">` while an
+ * English note in the same build renders English chrome. `translate` falls back
+ * to the navigation language for an entry carrying no `language`, which is the
+ * published corpus's single note.
+ */
+const t = translate(entry.language);
+
+/**
+ * This page's language as an actual tag, which is what `<html lang>` carries and
+ * what a listed foreign title is compared against.
+ *
+ * `entry.language` is optional and `translate` resolves that to the navigation
+ * language; this resolves it to the same value so that a note declaring none and
+ * a note declaring `en` mark exactly the same set of foreign titles. Passing
+ * `entry.language` raw would compare `undefined` against `'en'` and put a
+ * redundant `lang="en"` on every English title on the published corpus.
+ */
+const lang = entry.language ?? NAV_LANGUAGE;
+// The renderer takes this mapping rather than knowing the route shape itself,
+// so `/notes/<slug>/` is defined in exactly one place. Returning undefined for
+// an unpublished slug leaves that href untouched rather than pointing it at a
+// route that does not exist.
+//
+// `pageTitle` is what lets the anatomy put the title above the article: the
+// producer writes it into the body as a leading `# Title`, and the renderer
+// drops that one duplicate rather than the page rendering it twice. A body that
+// keeps some *other* `h1` is left alone and fails the "exactly one h1" gate,
+// which is the honest outcome — see `RenderOptions.pageTitle`.
+const { html, toc, hasCode, hasMath, hasMermaid } = await renderMarkdown(entry.markdown, {
+  pageTitle: entry.title,
+  routeForSlug: (slug) => (getEntry(slug) ? noteRoute(slug) : undefined),
+  // The two strings the renderer writes into the article that are this
+  // repository's words rather than the author's: a heading anchor's accessible
+  // name and an untitled diagram's caption. They are chrome, so they follow the
+  // document like every other chrome string — a Chinese article had English
+  // accessible names on every heading before TK-16 threaded this through.
+  chrome: t,
+});
+
+/**
+ * `Home / Notes / <collection> / <title>`, from public fields only.
+ *
+ * `collection` is validated as a flat slug and there is no hierarchy behind it,
+ * so the trail is at most four deep. TK-05c owns the collection tree; when it
+ * lands, this gains ancestors and nothing else changes. The `/#notes` target is
+ * the home page's own listing — requirements section 9.1 defines no `/notes/`
+ * index, and `PRIMARY_NAV` already points there.
+ *
+ * Every segment is a fixed route or an artifact field. Nothing reads a path, so
+ * a breadcrumb can never disclose a private folder name.
+ */
+const collection = entry.collection;
+const breadcrumbs: { label: string; href?: string }[] = [
+  { label: t.navHome, href: '/' },
+  { label: t.navNotes, href: '/#notes' },
+  ...(collection === undefined ? [] : [{ label: collection, href: collectionRoute(collection) }]),
+  { label: entry.title },
+];
+
+/**
+ * The calendar date a reader sees, from an artifact date.
+ *
+ * The first ten characters, not a parsed and reformatted `Date`. TK-01 has
+ * already validated both fields as ISO 8601, so the prefix *is* the calendar
+ * date exactly as the producer wrote it — and taking it verbatim avoids the two
+ * ways formatting gets this wrong: a date-only value parsed as UTC midnight and
+ * rendered in the build machine's zone shows the previous day west of
+ * Greenwich, and a locale format would be a chrome string TK-16 then has to
+ * translate. `YYYY-MM-DD` is unambiguous in both of this site's languages.
+ *
+ * The `<time datetime>` attribute carries the full precise value, so nothing
+ * the artifact expressed is lost.
+ */
+function displayDate(value: string): string {
+  return value.slice(0, 10);
+}
+
+const canonicalRoute = noteRoute(entry.slug);
+
+/**
+ * The three relationship surfaces, resolved once.
+ *
+ * `outgoing` and `backlinks` are the artifact's authored edges; `related` is
+ * derived and says so on the page. All three are computed here rather than in
+ * the template so that the markup below reads as the anatomy it is.
+ *
+ * **The incompleteness this used to state is gone, and the heading still says
+ * "Links to".** The producer derived `outgoing` from wikilinks only, so a plain
+ * Markdown link rendered a live `<a>` with no edge behind it. Since TK-27 one
+ * traversal produces the rewritten href *and* the edge from a single
+ * resolution (`scripts/resolve-links.ts`), across all five link forms — so that
+ * direction of disagreement is now unrepresentable rather than merely untested.
+ *
+ * The heading is unchanged deliberately, because "every link on this page"
+ * would be a lie in three ways the data still cannot support. An external link
+ * is an anchor a reader can click and is never an edge. A link that resolved to
+ * nothing, and one to a note the user withheld, are both on the page as the
+ * author's own words — degraded to text rather than deleted — and neither
+ * reaches anything here. And a link to this page's own heading renders as a
+ * real anchor inside the article while contributing no edge, because an entry
+ * may not link to itself. "Links to" describes the list that is actually there:
+ * the published notes this one reaches.
+ *
+ * What did change is the *empty* state, from possibly-false to true.
+ * `outgoingEmpty` reads "This note links to no other published note", and
+ * before TK-27 that sentence was printed for a note whose body was full of
+ * Markdown-syntax links to published notes. Now it can only be printed when it
+ * holds. `tests/backlink-surfaces.test.ts` gates it over a built site, which
+ * nothing did before — an empty state that states a fact was the one region
+ * here with no gate on the fact.
+ */
+const outgoing = notesForSlugs(entry.outgoing, getEntry);
+const backlinks = notesForSlugs(entry.backlinks, getEntry);
+const facets = tagFacets();
+const related = relatedNotes(entry, entries, facets);
+
+/**
+ * Why the related list is empty, when it is.
+ *
+ * Two different facts produce the same empty list and a reader deserves to be
+ * told which: a note with no tag-sharer anywhere, and a note whose every
+ * tag-sharer is already rendered in the two sections above. Saying "nothing
+ * shares a tag" in the second case is a claim the artifact contradicts, which
+ * is precisely what an honest empty state must not do.
+ *
+ * `hasTagPeer` runs only for an empty list, which is the only case
+ * `LinkedNotes` renders the message; a page with related notes skips a second
+ * full scan of the facet index.
+ */
+const relatedEmpty =
+  related.length === 0 && !hasTagPeer(entry, entries, facets)
+    ? t.relatedNoTagPeer
+    : t.relatedAlreadyListed;
+
+/**
+ * The pager: its two links and the name it announces, or nothing at all.
+ *
+ * One value rather than a neighbour pair plus a separate label, so the template
+ * has a single condition to branch on. Two conditions is how a pager ends up
+ * rendered as an empty `<nav>` for the one shape neither corpus contains — a
+ * note alone in its collection. `collectionNeighbours` returns no neighbour for
+ * that case and `tests/relations.test.ts` pins it; this keeps the page from
+ * being able to disagree.
+ *
+ * Naming the collection matters because a page carries several `<nav>` elements
+ * and a screen reader lists them by name.
+ */
+const neighbours = collectionNeighbours(entry, entries);
+const pager =
+  collection !== undefined && (neighbours.previous !== undefined || neighbours.next !== undefined)
+    ? { ...neighbours, label: t.moreInCollection(collection) }
+    : undefined;
+
+/**
+ * § 9.2.11's neighbourhood, laid out during the build.
+ *
+ * The same edges the two lists above render, drawn as a figure — plus the edges
+ * *between* those neighbours, which is what makes it a graph rather than a
+ * picture of a list. `checkCorpus` has already proven every one of them
+ * resolves, which is why the layout is affordable here and structurally
+ * unavailable to a whole-vault renderer.
+ */
+const graph = localGraph(entry, getEntry);
+---
+
+<Layout
+  title={`${entry.title}${TITLE_SUFFIX}`}
+  description={entry.excerpt}
+  lang={entry.language}
+>
+  {/*
+    Owner decision 7, the live case. Each flag is true only when the body
+    contains the construct, so each sheet reaches only the pages that render
+    one. Three conditional `<link>` elements rather than one merged sheet:
+    merging Mermaid's per-diagram-type stylesheets was measured at 6,354 B gzip
+    against a 972 B median for a single type, and the build-time renderer
+    removes the need for either — `diagram.css` is 14 rules because the theming
+    is flattened onto the SVG itself.
+
+    `hasMath` also gates the ~9 KB Temml stylesheet and, through its
+    `unicode-range`, the 9.4 KB `Temml.woff2` — which a browser fetches only for
+    an expression that actually uses `\mathscr`.
+  */}
+  {hasCode && <link slot="head" rel="stylesheet" href={codeStylesheet} />}
+  {hasMath && <link slot="head" rel="stylesheet" href={mathStylesheet} />}
+  {hasMermaid && <link slot="head" rel="stylesheet" href={diagramStylesheet} />}
+  {/* The graph sheet reaches only a note that actually draws one — a note with
+      no neighbourhood renders a sentence and requests nothing. The published
+      corpus's single note is exactly that case. `hasDrawableGraph` is the same
+      predicate the component branches on, so the stylesheet and the figure
+      cannot disagree about whether there is a graph. */}
+  {hasDrawableGraph(graph) && <link slot="head" rel="stylesheet" href={graphStylesheet} />}
+  {/*
+    Client mode only, and only on a page that has a diagram.
+
+    Astro bundles a script tag **eagerly**: the `hasMermaid` condition decides
+    whether the tag is rendered, not whether the module is built. Keeping
+    Mermaid out of `dist/` in build-time mode is therefore done in
+    `astro.config.mjs`, which resolves `src/scripts/diagram.ts` to an empty stub
+    unless client mode is selected. Both halves are needed — this one so a
+    diagram-free page requests nothing, that one so a diagram-free *build*
+    contains nothing. `tests/math-and-diagrams.test.ts` asserts both over
+    `dist/`.
+
+    `DIAGRAM_MODE` is checked here as well, so build-time mode emits no tag at
+    all rather than one pointing at a 20-byte empty chunk. It is not what keeps
+    Mermaid out — the resolver is — but a request for nothing is still a
+    request.
+  */}
+  {hasMermaid && DIAGRAM_MODE === 'client' && (
+    <script>
+      import '../../scripts/diagram.js';
+    </script>
+  )}
+  {/*
+    The same arrangement for math, and it needs both halves for the same reason
+    the diagram one does: this condition keeps a math-free page from requesting
+    anything, and `astro.config.mjs`'s resolver keeps a build-time *build* from
+    containing Temml at all. `clientRuntimePlugin` is parameterised over the two
+    runtimes rather than duplicated.
+
+    `hasMath` needs no change to serve this: it is set in `mathPlugin` before the
+    mode branch, so it means "this page has an expression" in either mode — which
+    is what both the stylesheet above and this tag ask of it.
+  */}
+  {hasMath && MATH_MODE === 'client' && (
+    <script>
+      import '../../scripts/math.js';
+    </script>
+  )}
+
+  <header class="note-header">
+    {/* § 9.2.3 — the trail. Public fields only; never a private folder name. */}
+    <nav class="breadcrumbs" aria-label={t.breadcrumbLabel}>
+      <ol>
+        {breadcrumbs.map((crumb) => (
+          <li>
+            {crumb.href === undefined ? (
+              <span aria-current="page">{crumb.label}</span>
+            ) : (
+              <a href={crumb.href}>{crumb.label}</a>
+            )}
+          </li>
+        ))}
+      </ol>
+    </nav>
+
+    {/* § 9.2.4 — the title, and the public metadata the artifact actually
+        carries. Every row below is optional in the contract, so each is
+        conditional: a note with none of them renders a title and nothing else,
+        which is the published corpus today. */}
+    <h1 class="note-title">{entry.title}</h1>
+
+    {(entry.created !== undefined ||
+      entry.updated !== undefined ||
+      collection !== undefined ||
+      (entry.tags?.length ?? 0) > 0 ||
+      (entry.aliases?.length ?? 0) > 0) && (
+      <dl class="note-meta">
+        {entry.created !== undefined && (
+          <div>
+            <dt>{t.metaPublished}</dt>
+            <dd><time datetime={entry.created}>{displayDate(entry.created)}</time></dd>
+          </div>
+        )}
+        {entry.updated !== undefined && (
+          <div>
+            <dt>{t.metaUpdated}</dt>
+            <dd><time datetime={entry.updated}>{displayDate(entry.updated)}</time></dd>
+          </div>
+        )}
+        {collection !== undefined && (
+          <div>
+            <dt>{t.metaCollection}</dt>
+            <dd><a href={collectionRoute(collection)}>{collection}</a></dd>
+          </div>
+        )}
+        {entry.tags !== undefined && entry.tags.length > 0 && (
+          <div>
+            <dt>{t.metaTags}</dt>
+            <dd>
+              <ul class="note-tags">
+                {entry.tags.map((tag) => (
+                  <li><a href={tagRouteForLabel(tag)}>{tag}</a></li>
+                ))}
+              </ul>
+            </dd>
+          </div>
+        )}
+        {/* Pagefind searches metadata outside `data-pagefind-body`, so aliases
+            remain findable without becoming the body-derived result excerpt. */}
+        {entry.aliases !== undefined && entry.aliases.length > 0 && (
+          <div>
+            <dt>{t.metaAliases}</dt>
+            <dd>
+              <ul class="note-aliases" data-pagefind-meta="aliases">
+                {entry.aliases.map((alias) => <li>{alias}</li>)}
+              </ul>
+            </dd>
+          </div>
+        )}
+      </dl>
+    )}
+
+    {/* § 9.2.5 — the optional summary.
+        `description` verbatim, with no comparison against `excerpt`: the two
+        are separate artifact fields, the excerpt is never rendered on this page
+        (it is the `<meta name="description">` and the card body elsewhere), and
+        a note whose author wrote the same sentence into both still asked for a
+        summary. Suppressing on equality was tried and was a product decision
+        this ticket has no reason to make. */}
+    {entry.description !== undefined && <p class="note-summary">{entry.description}</p>}
+  </header>
+
+  {/* § 9.2.6 — the table of contents, on pages above `TOC_MIN_HEADINGS`. The
+      renderer returns an empty `toc` below the threshold, so the threshold
+      lives in one place and this is only the rendering decision. */}
+  {toc.length > 0 && <TableOfContents entries={toc} isRoot lang={entry.language} />}
+
+  {/* § 9.2.7 — the sanitized article body. */}
+  <article
+    class="prose"
+    data-pagefind-body
+    data-code-copy={t.codeCopy}
+    data-code-copied={t.codeCopied}
+    data-code-copy-failed={t.codeCopyFailed}
+  >
+    <div set:html={html} />
+  </article>
+
+  {/* § 9.2.8 — outgoing public links: the notes this one links to, by title.
+      Every target is a published entry — `checkCorpus` proves it — so this can
+      never be a dead link or a private title. */}
+  <LinkedNotes
+    region="outgoing"
+    heading={t.outgoingHeading}
+    entries={outgoing}
+    empty={t.outgoingEmpty}
+    lang={lang}
+  />
+
+  {/* § 9.2.9 — static backlinks. Requirements section 13.1 asks for five
+      things: source title, source route, an optional source heading, a bounded
+      sanitized context excerpt, and a stable sort order. Three are rendered.
+      The heading and the context excerpt are not, because the artifact carries
+      one slug per edge and nothing about *where* in the source that edge is —
+      no heading, no offset, no surrounding text.
+
+      `ContentEntry.excerpt` is deliberately not substituted for the missing
+      one. It is the source note's own summary — the same string the card, the
+      `<meta name="description">`, and the hover preview all use — and it is
+      derived from the note's opening, not from the passage that links here.
+      Printed under a backlink it would read as the context of the link while
+      being unrelated to it, which is the fabrication the empty states exist to
+      avoid: a wrong answer presented in the shape of a right one is worse than
+      no answer. A real context excerpt needs a per-edge field; that is TK-19's
+      producer contract work. */}
+  <LinkedNotes
+    region="backlinks"
+    heading={t.backlinksHeading}
+    entries={backlinks}
+    empty={t.backlinksEmpty}
+    lang={lang}
+  />
+
+  {/* § 9.2.10 — the related-note fallback. Derived, not authored, and the
+      markup says so: the rule is stated below the heading so a reader is never
+      left to guess whether the owner put these here. `relations.ts` documents
+      the rule and the alternatives it was chosen over. */}
+  <LinkedNotes
+    region="related"
+    heading={t.relatedHeading}
+    entries={related}
+    empty={relatedEmpty}
+    derivation={t.relatedDerivation}
+    lang={lang}
+  />
+
+  {/* § 9.2.11 — the local-graph neighborhood: build-time inline SVG with real
+      `<a>` elements plus the equivalent table section 17 requires. TK-21's
+      interactive layer must not be stubbed in here — this is the baseline that
+      survives when that enhancement fails. */}
+  <NoteGraph
+    graph={graph}
+    region="note-graph"
+    heading={t.graphHeading}
+    derivation={t.graphLocalDerivation}
+    empty={t.graphEmpty}
+    bounded={t.graphBoundedLocal}
+    expand={{
+      href: `/${GRAPH_SEGMENT}/`,
+      text: t.graphExpandLocal,
+      label: t.graphExpandLocalLabel,
+    }}
+    lang={lang}
+    explore={{ scope: 'local', centerSlug: entry.slug }}
+  />
+
+  {/* § 9.2.12 — collection navigation, "where meaningful": only inside a
+      collection that has another note, and in the same order
+      `/collections/<key>/` lists them. A note with no collection, or the only
+      note in one, renders nothing rather than a pager with two dead ends. */}
+  {pager !== undefined && (
+    <nav class="collection-pager" aria-label={pager.label}>
+      {/* The link carries the destination's own title, so it is a meaningful
+          link out of context — "Previous" alone would be four identical link
+          names on a screen reader's link list. The direction word is a
+          separate element rather than part of the link text for the same
+          reason — and the title carries its own `lang` when the neighbour is in
+          another language, which the direction word never is. */}
+      {pager.previous !== undefined && (
+        <a href={noteRoute(pager.previous.slug)} rel="prev">
+          <span class="pager-direction">{t.pagerPrevious}</span>
+          <span
+            class="pager-title"
+            lang={partLanguage(pager.previous.language, lang)}
+          >{pager.previous.title}</span>
+        </a>
+      )}
+      {pager.next !== undefined && (
+        <a class="pager-next" href={noteRoute(pager.next.slug)} rel="next">
+          <span class="pager-direction">{t.pagerNext}</span>
+          <span
+            class="pager-title"
+            lang={partLanguage(pager.next.language, lang)}
+          >{pager.next.title}</span>
+        </a>
+      )}
+    </nav>
+  )}
+
+  {/* § 9.2.13 — the footer: public provenance and the canonical route. */}
+  <footer class="note-footer">
+    <p>{t.noteProvenance}</p>
+    {/* TK-08 configured `site:`, so this is the full canonical URL rather than
+        the route TK-05a could honestly emit. A reader who copies it from a
+        printed or quoted page gets an address that resolves. */}
+    <p class="note-canonical">{t.canonicalUrlLine(canonicalUrl(Astro.site, canonicalRoute))}</p>
+  </footer>
+</Layout>

package/src/pages/privacy.astro

@@ -0,0 +1,121 @@
+---
+/**
+ * What this site collects, which is nothing.
+ *
+ * **Rewritten by TK-31 for one false claim and one unsupportable one.** The
+ * previous version ended with "Every page here was individually reviewed and
+ * approved for publication. Material that was not approved is not represented
+ * on this site in any form." The first sentence describes the retired owner-specific bridge
+ * and is false of a build from a directory of Markdown; the second is *true*
+ * and had been resting on the first, so it read as a consequence of a review
+ * process rather than of what the build actually does.
+ *
+ * That distinction matters more here than on `/about/`. A privacy page is the
+ * document a reader consults to decide whether to trust the rest, so a claim in
+ * it that the tool cannot keep is worse than no page: it converts a technical
+ * guarantee into a promise about someone's diligence, and a reader has no way
+ * to tell which they were given.
+ *
+ * **Every claim below is a property this build enforces**, and each is scoped to
+ * what is actually held. `tests/built-output.test.ts` asserts every `<script>`
+ * in `dist/` is same-origin and none is inline; `public/_headers` sets a CSP
+ * whose `script-src`, `style-src`, `font-src`, and `connect-src` are all
+ * `'self'`. The absence of cookies and of analytics follows from there being no
+ * server and no such script.
+ *
+ * **`img-src` is the one directive that is not `'self'`** — it permits `https:`,
+ * so a note whose author embedded a remote image renders it, and that request
+ * reaches a third party. Measured, not inferred. The page therefore says
+ * "script, stylesheet, and font" where it once said "every asset", and names the
+ * image case separately: the earlier wording was a claim this build does not
+ * keep, on the page a reader consults to calibrate trust.
+ *
+ * The other thing this page cannot speak for is the host that serves the files,
+ * so it says who that is and stops rather than promising on their behalf.
+ *
+ * See `about.astro` for why this is still a shipped page rather than a note
+ * `init` seeds into the user's own repository.
+ *
+ * **The Content section was rewritten on 2026-08-17**, for the same reason the
+ * paragraphs above it were: it said an excluded note "produces no page, no
+ * search entry, and no link", and the last clause stopped being true when the
+ * owner made links to withheld notes live. It now says what a reader can
+ * actually observe — the link exists, it carries the note's own path as often
+ * as not, and it leads to a page that says the note is not published.
+ */
+import Layout from '../layouts/Layout.astro';
+import { DEFAULT_NAV_LANGUAGE } from '../lib/translations.js';
+import { TITLE_SUFFIX } from '../lib/site.js';
+---
+
+{/* The prose below is English whatever the site language, so the page says so. */}
+<Layout
+  title={`Privacy${TITLE_SUFFIX}`}
+  lang={DEFAULT_NAV_LANGUAGE}
+  description="No analytics, no comments, no third-party tracking."
+>
+  <article class="prose">
+    <h1>Privacy</h1>
+
+    <h2>What this site does not do</h2>
+
+    <p>
+      There are no analytics on this site. No page view, click, scroll, reading time, or search
+      query is measured, recorded, or reported anywhere.
+    </p>
+
+    <p>
+      There are no comments, reactions, accounts, or sign-in. There is nothing to submit and no
+      form to fill in.
+    </p>
+
+    <p>
+      No third-party tracking runs here. There are no advertising or analytics scripts, no
+      tracking pixels, no social widgets, and no embedded players. Every script, stylesheet, and
+      font a page loads comes from this site's own address.
+    </p>
+
+    <p>
+      Images are the exception, and only where a note's author linked one. A note that embeds an
+      image hosted elsewhere renders that image from wherever it lives, so displaying it tells that
+      host you loaded the page — the same as following a link there. Nothing on this site does that
+      on its own; it happens only where the writing itself points outward.
+    </p>
+
+    <p>
+      This site sets no cookies. Your theme and reader-mode choices are stored by your own browser,
+      on your own device, and are never sent anywhere. Clearing your browser's site data removes
+      them.
+    </p>
+
+    <h2>Search</h2>
+
+    <p>
+      Search runs entirely inside your browser against a search index served as a static file.
+      Nothing you type is transmitted to this site or to anyone else.
+    </p>
+
+    <h2>What is unavoidable</h2>
+
+    <p>
+      Requesting a page from any website necessarily reveals your IP address and browser details to
+      whoever serves it. This site is served by a static hosting provider, which may keep
+      operational request logs of its own under its own policy. Nothing beyond that is collected by
+      this site, which has no server of its own to collect it with.
+    </p>
+
+    <h2>Content</h2>
+
+    <p>
+      This site is generated from a set of notes, and a note excluded from it produces no page, no
+      search entry, and no content here. None of what it says appears. What does still appear is
+      the words a published note used to refer to it: a link pointing at an excluded note keeps its
+      own text — often the note's name and the path it had — and leads to a page saying the note is
+      not published. See <a href="/about/">About</a> for how that works.
+    </p>
+
+    <p>
+      If any of this changes, this page changes with it.
+    </p>
+  </article>
+</Layout>