ancient-fences 0.3.2 → 0.4.1

package/README.md

@@ -3,9 +3,17 @@
   <img src="https://raw.githubusercontent.com/Marcin1000/ancient-fences/main/assets/readme-banner-light.png" alt="Ancient Fences" width="100%">
 </picture>
 
+<p align="center">
+  <a href="https://www.npmjs.com/package/ancient-fences"><img alt="npm" src="https://img.shields.io/npm/v/ancient-fences?color=8B5514&labelColor=1E242B&style=flat-square"></a>
+  <img alt="MIT licence" src="https://img.shields.io/badge/licence-MIT-8B5514?labelColor=1E242B&style=flat-square">
+  <img alt="Node 20 or newer" src="https://img.shields.io/badge/node-%E2%89%A520-8B5514?labelColor=1E242B&style=flat-square">
+  <img alt="Works with Claude Code, Cursor and Copilot" src="https://img.shields.io/badge/output-agent%20tasks-8B5514?labelColor=1E242B&style=flat-square">
+</p>
+
 # Ancient Fences
 
-**Find the code you wrote because of someone else's bug. Then check whether that bug is still there.**
+**Find outdated workarounds in a long-lived codebase, and turn the verified ones
+into tasks a coding agent can act on.**
 
 Dependabot bumps the version. Nobody removes the workaround you wrote because
 the old version was broken.
@@ -13,14 +21,23 @@ the old version was broken.
 ```bash
 npx ancient-fences .           # what is standing in this codebase
 npx ancient-fences . --check   # and whether the reasons still hold
+npx ancient-fences . --tasks   # the dead ones, written as work for your agent
 ```
 
-No installation, no configuration, no account. It reads the repository you
-point it at and prints what it found.
+No installation, no configuration, no account. It reads the repository you point
+it at and prints what it found.
+
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/Marcin1000/ancient-fences/main/assets/shot-fences.png">
+  <img src="https://raw.githubusercontent.com/Marcin1000/ancient-fences/main/assets/shot-fences-light.png" alt="Ancient Fences output for webpack: 90 fences standing, 39 of them in tests, the oldest untouched for 8.8 years" width="100%">
+</picture>
+
+A real run against a full clone of webpack. Nothing here is typed to look good.
 
 ## The problem
 
-You hit a bug in a library. You write code around it and, if you are decent, leave a note:
+You hit a bug in a library. You write code around it and, if you are decent,
+leave a note:
 
 ```js
 // Workaround for https://github.com/some/lib/issues/2500 (remove when fixed)
@@ -28,14 +45,47 @@ You hit a bug in a library. You write code around it and, if you are decent, lea
 
 Then the bug gets fixed. The issue is closed. The library is replaced. And
 nothing happens, because there is no link between someone else's tracker and
-your code. The workaround stays forever, and after two years nobody dares
-touch it: the note says "bug", so maybe the bug is still there.
+your code. The workaround stays forever, and after two years nobody dares touch
+it: the note says "bug", so maybe the bug is still there.
 
 This is Chesterton's Fence at industrial scale. The code knows the fence is
-there. Git knows how long it has stood. Nobody checks whether the reason
-still exists.
+there. Git knows how long it has stood. Nobody checks whether the reason still
+exists.
+
+## From workaround to agent task
+
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/Marcin1000/ancient-fences/main/assets/diagram-fences.png">
+  <img src="https://raw.githubusercontent.com/Marcin1000/ancient-fences/main/assets/diagram-fences-light.png" alt="Three stages: detect the workaround, check the reason still holds, hand off a task an agent can act on" width="100%">
+</picture>
+
+Ancient Fences does not edit your code, and that is deliberate. Knowing that a
+fence is dead is the scarce part; every editor now ships something that can do
+the deleting. So `--tasks` writes the verified findings as work:
+
+```bash
+npx ancient-fences . --check --tasks
+```
+
+You get a markdown file with one entry per dead fence: the file and line, the
+reason originally recorded, what proves it no longer holds, and the instruction.
+Each entry has this shape:
+
+```markdown
+## src/upload.js:212
+
+- Recorded reason: github:some/lib#2500
+- Evidence: the issue was closed on 2021-04-14, and the fix shipped in
+  1.9.0 (milestone). Your lockfile has some-lib 2.3.1.
+- Untouched for 4.2 years.
 
-## Real example
+Remove the workaround and the comment that explains it, then run the test suite.
+```
+
+Point Claude Code, Cursor, Copilot or your own script at that file. The tests
+are the safety net, which is why every instruction ends there.
+
+## A real one, in full
 
 In `webpack`, `test/configCases/plugins/terser-plugin/extract.js:3`:
 
@@ -44,31 +94,36 @@ In `webpack`, `test/configCases/plugins/terser-plugin/extract.js:3`:
 // https://github.com/mishoo/UglifyJS2/issues/2500
 ```
 
-Written **2017-11-08**. The referenced issue is closed. Webpack dropped
-UglifyJS for terser in 2018. The string `uglify` does not appear in its
-`package.json` even once. The directory is literally named `terser-plugin`.
-The fence has stood untouched for **8.8 years**, guarding a hole in a road
-that no longer exists.
+The referenced issue is closed. Webpack dropped UglifyJS for terser in 2018, and
+the string `uglify` does not appear anywhere else in the repository. The
+directory is literally named `terser-plugin`. The line has stood untouched for
+**8.8 years**, guarding a hole in a road that no longer exists.
+
+That one lives in a test file, which is exactly why this tool would not ask you
+to delete it. Read on.
 
-Two runs, full clones, August 2026:
+## Tests are counted apart, and never listed as work
+
+A comment in a test that links to an issue is usually the regression test for
+that bug. It exists because of the bug, exactly like a workaround, but a closed
+issue is the reason to **keep** it.
+
+Four full clones, measured with this command:
 
 | Repository | In source | In tests | Oldest |
 |---|---|---|---|
 | puppeteer/puppeteer | 32 | 45 | 9.1 yr |
-| webpack/webpack | 54 | 39 | 8.8 yr |
+| webpack/webpack | 51 | 39 | 8.8 yr |
 | eslint/eslint | 43 | 399 | 8.2 yr |
 | expressjs/express | 0 | 2 | 1.9 yr |
 
-Both are well-maintained projects by good engineers. That is the point.
-
-Measured on a full clone, because a shallow one cannot date a line.
+eslint has 399 findings in tests and 43 in its source. One combined number would
+have made it look ten times worse than it is, and would have told an agent to
+delete the tests that guard fixed bugs.
 
-The two columns are the point. A comment in a test that links to an issue is
-usually the regression test for that bug: it exists because of the bug, exactly
-like a workaround, but a closed issue is the reason to **keep** it. eslint has
-399 of those and 43 in its source. Mixing them into one number would have made
-eslint look ten times worse than it is, and would have told an agent to delete
-the tests that guard fixed bugs.
+All four are maintained by good engineers. That is the point. The full reports
+are published at
+[ancientcode.net/reports](https://ancientcode.net/reports/).
 
 ## What it finds
 
@@ -82,11 +137,11 @@ the tests that guard fixed bugs.
 A comment counts as a fence when it links to an external tracker, or says
 something that only a fence says ("workaround", "kludge", "no longer needed",
 "do not upgrade"). Words that merely appear in fences ("until", "polyfill",
-"temporary", "regression") count only when the comment also names the
-condition: a deadline or a version. Phrases that read as prose elsewhere
-("remove this", "blocked by") count next to a `TODO`, `FIXME` or `HACK`, or
-next to a named condition. Comment markers are read per language, so `#fff` in
-a stylesheet and `a // b` in Python are not comments.
+"temporary", "regression") count only when the comment also names the condition:
+a deadline or a version. Phrases that read as prose elsewhere ("remove this",
+"blocked by") count next to a `TODO`, `FIXME` or `HACK`, or next to a named
+condition. Comment markers are read per language, so `#fff` in a stylesheet and
+`a // b` in Python are not comments.
 
 Trackers understood: GitHub issues and pull requests, Chromium (`crbug.com`),
 Mozilla Bugzilla, WebKit.
@@ -105,8 +160,8 @@ VERDICT:  upgrade first (fix shipped in 0.34.0, but sharp is pinned at 0.33.1)
 ```
 
 Those are two different jobs. The first is code you can delete this afternoon.
-The second is the more uncomfortable finding: you are still paying to maintain
-a workaround for a bug that was fixed years ago, because nobody upgraded.
+The second is the more uncomfortable finding: you are still paying to maintain a
+workaround for a bug that was fixed years ago, because nobody upgraded.
 
 `package-lock.json`, `yarn.lock` and `pnpm-lock.yaml` are read when present. No
 lockfile means the tool says less, never something false.
@@ -117,8 +172,21 @@ was fetched, so the report says age was not measured rather than printing a
 confident zero.
 
 **An unknown issue state never produces `still valid`.** Not knowing is not a
-green light. A tool that reassures you without grounds is worse than no tool.
-(The test enforcing this caught a real bug on the prototype's first run.)
+green light, and when the tracker cannot answer the report says why. A tool that
+reassures you without grounds is worse than no tool.
+
+## A report you can forward
+
+```bash
+npx ancient-fences . --check --report=fences.html
+```
+
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/Marcin1000/ancient-fences/main/assets/report-fences.png">
+  <img src="https://raw.githubusercontent.com/Marcin1000/ancient-fences/main/assets/report-fences-light.png" alt="The HTML report: counts, then the longest-untouched fences with their recorded reasons" width="100%">
+</picture>
+
+One HTML file, no scripts, no external requests.
 
 ## Options
 
@@ -137,45 +205,12 @@ green light. A tool that reassures you without grounds is worse than no tool.
                     (default 7)
 ```
 
-An option this tool does not recognise stops the run. A mistyped `--chek`
-used to print a normal report, and the reader believed the trackers had been
-consulted.
-
-You can also point it at a single file: `npx ancient-fences src/thing.js`.
-
-Bundles committed into a repository (`vendor.js`, a browserify or webpack
-build, anything minified) are skipped, and the summary says how many were left
-out. The fences inside them belong to the libraries they were built from, so
-listing them buries the ones your team can actually act on. `dist`, `build`,
-`node_modules`, `vendor` and `third_party` are skipped for the same reason.
-
-Issue states are cached in your user cache directory (`$XDG_CACHE_HOME`,
-`%LOCALAPPDATA%`, or `~/.cache`), never inside the repository being scanned.
-Every entry records when it was read, entries older than a week are re-checked,
-and if the tracker cannot be reached the report says which day the answer is
-from:
-
-```
-VERDICT:  remove (reason disappeared 2021-04-02 (state as of 2026-08-18))
-```
-
-An issue state is a snapshot, not a fact. Closed issues get reopened.
-
-## Working with an agent
-
-Ancient Fences does not edit your code, and that is deliberate. Knowing that a
-fence is dead is the scarce part; every editor now ships something that can do
-the deleting. So `--tasks` writes the verified findings as work:
-
-```bash
-npx ancient-fences . --check --tasks
-```
+An unknown option, or a number where a number cannot go, stops the run with exit
+code 2 rather than being ignored. A mistyped flag that still prints a confident
+report is worse than no report.
 
-You get a markdown file with one entry per dead fence: the file and line, the
-reason originally recorded, what proves it no longer holds, and the instruction
-("remove the workaround and the comment, then run the test suite"). Point Claude
-Code, Cursor, Copilot or your own script at it. The tests are the safety net,
-which is why the instruction always ends there.
+An issue state is a snapshot, not a fact. Closed issues get reopened, which is
+why every cached state carries the date it was read.
 
 ## Tests
 
@@ -198,9 +233,13 @@ pull requests.
 ## Ancient Code
 
 Ancient Fences answers one question about one repository. The same blindness
-applies to everything else nobody re-checks in a long-running codebase: what
-was already paid for, which parts only one person understands, whether the
-whole thing could be handed to another team at all. That is
-[Ancient Code](https://ancientcode.net). This tool is its open-source front door.
+applies to everything else nobody re-checks in a long-running codebase: which
+parts only one person understands, whether it builds from scratch, whether the
+documentation still describes the system. [Ancient Code](https://ancientcode.net)
+asks all of them, ships this scanner inside it, and is free and open source too:
+
+```bash
+npx ancient-code .
+```
 
 MIT licensed.

package/bin/ancient-fences.mjs

@@ -8,6 +8,7 @@ import { detectFences } from '../src/detect.mjs';
 import { blameAll, historyDepth } from '../src/age.mjs';
 import { checkGithubRefs, verdict } from '../src/tracker.mjs';
 import { renderText, renderHtml, renderTasks, summarize } from '../src/report.mjs';
+import { projectName } from '../src/name.mjs';
 import { readInstalled } from '../src/lockfile.mjs';
 
 const args = process.argv.slice(2);
@@ -164,7 +165,10 @@ summary.skippedFiles = skipped;
 summary.history = history;
 summary.checkedAt = checking ? checkTimestamp(states) : null;
 
-const name = single ? basename(single) : basename(root);
+// Scanning one file, its own name is the subject. Scanning a repository, the
+// folder is the last resort: a full clone of webpack in webpackfull/ produced
+// a report titled "webpackfull".
+const name = single ? basename(single) : await projectName(root);
 
 const reportFlag = flags.find((f) => f === '--report' || f.startsWith('--report='));
 if (reportFlag) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ancient-fences",
-  "version": "0.3.2",
+  "version": "0.4.1",
   "description": "Finds the code you wrote because of someone else's bug, and checks whether that bug is still there.",
   "type": "module",
   "bin": {
@@ -25,7 +25,7 @@
   },
   "license": "MIT",
   "scripts": {
-    "test": "node test/detect.test.mjs && node test/tracker.test.mjs && node test/versions.test.mjs && node test/lockfile.test.mjs && node test/paths.test.mjs && node test/walk.test.mjs && node test/cli.test.mjs"
+    "test": "node test/detect.test.mjs && node test/tracker.test.mjs && node test/versions.test.mjs && node test/lockfile.test.mjs && node test/paths.test.mjs && node test/walk.test.mjs && node test/stylesheet.test.mjs && node test/cli.test.mjs"
   },
   "repository": {
     "type": "git",

package/src/name.mjs

@@ -0,0 +1,52 @@
+import { execFile } from 'node:child_process';
+import { promisify } from 'node:util';
+import { readFile } from 'node:fs/promises';
+import { join, basename } from 'node:path';
+
+const run = promisify(execFile);
+
+/**
+ * What to call the repository in a report somebody forwards.
+ *
+ * The folder name is the worst of the three answers and used to be the only
+ * one: a full clone of webpack sitting in webpackfull/ produced a report
+ * titled "webpackfull". The remote knows the real name, the manifest knows the
+ * published one, and the folder is only the last resort.
+ */
+export async function projectName(root) {
+  const remote = await gitRemote(root);
+  if (remote) return remote;
+
+  const pkg = await readJson(join(root, 'package.json'));
+  if (pkg?.name) return pkg.name;
+
+  return basename(root);
+}
+
+async function readJson(path) {
+  try {
+    return JSON.parse(await readFile(path, 'utf8'));
+  } catch {
+    return null;
+  }
+}
+
+async function gitRemote(root) {
+  try {
+    const { stdout } = await run('git', ['remote', 'get-url', 'origin'], { cwd: root });
+    return ownerRepo(stdout.trim());
+  } catch {
+    return null;
+  }
+}
+
+/** "git@github.com:webpack/webpack.git" and the https form both give webpack/webpack. */
+export function ownerRepo(url) {
+  if (!url) return null;
+  const clean = String(url).trim().replace(/\.git$/, '').replace(/\/+$/, '');
+  const m = /[:/]([^/:]+)\/([^/]+)$/.exec(clean);
+  if (!m) return null;
+  // A local path clone has no owner worth printing, only a directory above it.
+  if (/^(\.|\/|[a-z]:\\)/i.test(clean) || clean.startsWith('file:')) return null;
+  return `${m[1]}/${m[2]}`;
+}

package/src/report.mjs

@@ -149,6 +149,11 @@ export function renderText(fences, summary, repoName, checked = false) {
     for (const [level, count] of Object.entries(summary.verdicts).sort((a, b) => b[1] - a[1])) {
       L.push(`  ${String(count).padStart(4)}  ${level}`);
     }
+    // "unchecked" on its own reads as a bug in this tool. The reason was
+    // recorded and then thrown away before anybody could see it.
+    for (const [why, count] of unreachable(fences)) {
+      L.push(`        ${count} of them because the tracker could not answer: ${why}`);
+    }
     L.push('');
   }
 
@@ -192,6 +197,22 @@ export function renderText(fences, summary, repoName, checked = false) {
   return L.join('\n');
 }
 
+/**
+ * Why the tracker could not answer, grouped and counted. Rate limiting, no
+ * network and a repository that needs a token all land here, and each one is
+ * something the reader can act on. Silence is not.
+ */
+export function unreachable(fences) {
+  const reasons = new Map();
+  for (const f of fences) {
+    const why = f.verdict?.why;
+    if (f.verdict?.level !== 'unchecked' || !why) continue;
+    if (/no recorded reason/.test(why)) continue;
+    reasons.set(why, (reasons.get(why) ?? 0) + 1);
+  }
+  return [...reasons.entries()].sort((a, b) => b[1] - a[1]);
+}
+
 const esc = (s) => String(s).replace(/[&<>"]/g, (c) => ({ '&': '&amp;', '<': '&lt;', '>': '&gt;', '"': '&quot;' }[c]));
 
 /**
@@ -212,10 +233,10 @@ export function renderHtml(fences, summary, repoName, checked = false) {
     const y = yearsSince(f.lastTouched);
     const v = f.verdict;
     return `<tr>
-      <td class="num">${y === null ? '-' : y.toFixed(1) + ' yr'}</td>
-      <td><code>${esc(f.file)}:${f.line}</code><p>${esc(f.text.slice(0, 130))}</p></td>
-      <td class="num">${esc(premiseOf(f))}</td>
-      <td>${showVerdict(f, checked) ? `<span class="v v-${esc(v.level.replace(/\s+/g, '-'))}">${esc(v.level)}</span><p>${esc(v.why)}</p>` : '<span class="v">not checked</span>'}</td>
+      <td data-label="Untouched" class="num">${y === null ? '-' : y.toFixed(1) + ' yr'}</td>
+      <td data-label="Where"><code>${esc(f.file)}:${f.line}</code><p>${esc(f.text.slice(0, 130))}</p></td>
+      <td data-label="Reason given" class="num">${esc(premiseOf(f))}</td>
+      <td data-label="${checked ? 'Verdict' : 'State'}">${showVerdict(f, checked) ? `<span class="v v-${esc(v.level.replace(/\s+/g, '-'))}">${esc(v.level)}</span><p>${esc(v.why)}</p>` : '<span class="v">not checked</span>'}</td>
     </tr>`;
   }).join('\n');
 
@@ -224,8 +245,8 @@ export function renderHtml(fences, summary, repoName, checked = false) {
 <meta name="viewport" content="width=device-width,initial-scale=1">
 <title>Ancient Fences: ${esc(repoName)}</title>
 <style>
-:root{--ground:#0F1216;--surface:#171C22;--surface2:#1E242B;--line:#2B333B;--ink:#E7E1D4;--dim:#A7A69C;--muted:#83877F;--gold:#E0A45C;--inst:#8FC3D2}
-@media (prefers-color-scheme:light){:root{--ground:#E3E2DC;--surface:#EDEBE4;--surface2:#F3F1EB;--line:#CFCCC1;--ink:#1A1E22;--dim:#4A4F53;--muted:#6B6F68;--gold:#8F5B18;--inst:#2E6B7C}}
+:root{--ground:#0F1216;--surface:#171C22;--surface2:#1E242B;--line:#2B333B;--ink:#E7E1D4;--dim:#A7A69C;--muted:#878B83;--gold:#E0A45C;--inst:#8FC3D2}
+@media (prefers-color-scheme:light){:root{--ground:#E3E2DC;--surface:#EDEBE4;--surface2:#F3F1EB;--line:#CFCCC1;--ink:#1A1E22;--dim:#4A4F53;--muted:#62665F;--gold:#8B5514;--inst:#2E6B7C}}
 *{box-sizing:border-box}
 body{margin:0;background:var(--ground);color:var(--ink);font:16px/1.6 ui-sans-serif,system-ui,-apple-system,"Segoe UI",Roboto,sans-serif;-webkit-font-smoothing:antialiased}
 .wrap{max-width:68rem;margin:0 auto;padding:0 clamp(1rem,4vw,2.5rem)}
@@ -239,13 +260,20 @@ h1{font:300 clamp(2rem,5vw,3.2rem)/1.05 ui-serif,Georgia,serif;letter-spacing:-.
 .stat b{font:400 2rem/1 ui-monospace,monospace;color:var(--gold);font-variant-numeric:tabular-nums}
 .stat span{font-size:.78rem;color:var(--dim);line-height:1.35}
 h2{font:300 1.6rem/1.1 ui-serif,Georgia,serif;margin:2.5rem 0 1rem}
+.brand{display:flex;align-items:center;gap:.6rem;color:var(--ink);margin-bottom:1.4rem}
+.brand span{font:300 1.2rem/1 ui-serif,Georgia,serif;transform:translateY(.09em)}
+.brand b{color:var(--gold);font-weight:300}
 .scroll{overflow-x:auto;border:1px solid var(--line);background:var(--surface)}
 table{border-collapse:collapse;width:100%;min-width:40rem;font-size:.88rem;table-layout:fixed}
 th,td{text-align:left;padding:.8rem 1rem;border-bottom:1px solid var(--line);vertical-align:top}
 thead th{font-family:ui-monospace,monospace;font-size:.64rem;letter-spacing:.12em;text-transform:uppercase;color:var(--muted);font-weight:400;background:var(--surface2);white-space:nowrap}
 td p{margin:.35rem 0 0;color:var(--dim);font-size:.82rem}
 td.num{color:var(--dim);font-variant-numeric:tabular-nums;font-size:.8rem;overflow-wrap:anywhere}
-col.age{width:6rem}col.reason{width:14rem}col.state{width:12rem}
+/* github:microsoft/TypeScript#41697 is 30 characters, and at 14rem it broke in
+   the middle of the word. A tracker id split across two lines is not an id
+   anybody can search for. Measured on webpack: 29 of 40 broke at 14rem, 2 at
+   19rem, and widening further changed nothing. */
+col.age{width:6rem}col.reason{width:19rem}col.state{width:11rem}
 code{overflow-wrap:anywhere}
 code{font-size:.82rem;color:var(--ink)}
 .v{font-family:ui-monospace,monospace;font-size:.7rem;letter-spacing:.06em;text-transform:uppercase;color:var(--muted)}
@@ -254,9 +282,31 @@ code{font-size:.82rem;color:var(--ink)}
 footer{border-top:1px solid var(--line);margin-top:3rem;padding:2rem 0 4rem;color:var(--muted);font-size:.85rem}
 footer strong{color:var(--ink)}
 footer p{max-width:62ch}
+/* Four columns of file paths never fit on a phone. Forced side by side, one
+   column collapses to nothing and its text prints a letter per line. Below this
+   width every row becomes a small block with its label in front. */
+@media (max-width:640px){
+  .scroll{overflow-x:visible}
+  table,tbody{display:block;width:100%;min-width:0}
+  thead{position:absolute;width:1px;height:1px;overflow:hidden;clip:rect(0 0 0 0);white-space:nowrap}
+  tr{display:flex;flex-wrap:wrap;border-bottom:1px solid var(--line);padding:.55rem .2rem}
+  tr:last-child{border-bottom:0}
+  td{display:block;flex:1 1 100%;min-width:0;border-bottom:0;padding:.3rem 1rem;overflow-wrap:anywhere}
+  td.num{flex:0 0 auto;min-width:7rem;max-width:100%;white-space:normal}
+  td[data-label]::before{display:block;content:attr(data-label);font-family:ui-monospace,monospace;font-size:.6rem;letter-spacing:.12em;text-transform:uppercase;color:var(--muted);margin-bottom:.15rem}
+}
 </style></head><body>
 <header><div class="wrap">
-  <p class="mono">Ancient Fences · ${esc(new Date().toISOString().slice(0, 10))}</p>
+  <div class="brand">
+    <svg viewBox="0 0 24 24" width="26" height="26" aria-hidden="true">
+      <rect x="2.6" y="3.2" width="18.8" height="2.4" fill="currentColor"/>
+      <rect x="5.6" y="7.4" width="2.4" height="13.4" fill="currentColor"/>
+      <rect x="10.8" y="7.4" width="2.4" height="13.4" fill="currentColor"/>
+      <rect x="16" y="7.4" width="2.4" height="13.4" fill="currentColor"/>
+      <rect x="3.4" y="12.6" width="17.2" height="1.8" fill="var(--gold)"/>
+    </svg><span>Ancient <b>Fences</b></span>
+  </div>
+  <p class="mono">Scanned ${esc(new Date().toISOString().slice(0, 10))}</p>
   <h1>${esc(repoName)}</h1>
   <p class="sub">Code that exists because of an external problem, and whether that problem is still there.</p>
 </div></header>
@@ -272,6 +322,7 @@ footer p{max-width:62ch}
   ${summary.history && summary.history.usable === false ? `<p class="sub">Age was not measured: ${esc(summary.history.why)}.</p>` : ''}
   ${summary.checkedAt ? `<p class="sub">Issue states read ${esc(summary.checkedAt.newest.slice(0, 10))}.</p>` : ''}
   ${!checked && summary.trackers > 0 ? `<p class="sub">The trackers were not consulted in this run, so the state column is empty. <code>--check</code> asks them whether these issues are still open.</p>` : ''}
+  ${checked && unreachable(fences).length ? `<p class="sub">The tracker could not answer for ${unreachable(fences).reduce((a, [, n]) => a + n, 0)} of these: ${esc(unreachable(fences).map(([why, n]) => `${n} × ${why}`).join(', '))}. Their state is unknown, which is not the same as still valid.</p>` : ''}
   ${summary.total === 0 ? `<h2>Nothing found</h2>
   <p class="sub">No comment in this codebase records an external reason for the code around it: no tracker link, no deadline, no note about a workaround. That is either a clean codebase or an undocumented one, and this tool cannot tell those apart.</p>` : `<h2>Check these first</h2>
   <div class="scroll"><table>
@@ -282,13 +333,13 @@ footer p{max-width:62ch}
   ${fences.length ? `<h2>Where they are</h2>
   <div class="scroll"><table>
     <thead><tr><th>File</th><th>Fences</th><th>Kinds</th></tr></thead>
-    <tbody>${byFile(fences, 15).map((r) => `<tr><td><code>${esc(r.file)}</code></td><td class="num">${r.total}</td><td class="num">${esc(Object.entries(r.kinds).map(([k, n]) => `${n} ${k}`).join(', '))}</td></tr>`).join('\n')}</tbody>
+    <tbody>${byFile(fences, 15).map((r) => `<tr><td data-label="File"><code>${esc(r.file)}</code></td><td data-label="Fences" class="num">${r.total}</td><td data-label="Kinds" class="num">${esc(Object.entries(r.kinds).map(([k, n]) => `${n} ${k}`).join(', '))}</td></tr>`).join('\n')}</tbody>
   </table></div>` : ''}
   ${summary.skipped ? `<h2>Left out</h2>
   <p class="sub">${summary.skipped} file${summary.skipped === 1 ? ' was' : 's were'} skipped as a build product. The fences inside a bundle belong to the libraries it was built from, not to this team.</p>
   <div class="scroll"><table>
     <thead><tr><th>File</th><th>Why</th></tr></thead>
-    <tbody>${(summary.skippedFiles ?? []).map((f) => `<tr><td><code>${esc(f.path)}</code></td><td class="num">${esc(f.why)}</td></tr>`).join('\n')}</tbody>
+    <tbody>${(summary.skippedFiles ?? []).map((f) => `<tr><td data-label="File"><code>${esc(f.path)}</code></td><td data-label="Why" class="num">${esc(f.why)}</td></tr>`).join('\n')}</tbody>
   </table></div>` : ''}
 </main>
 <footer><div class="wrap">