wiki-formant 0.17.1 → 0.18.0

package/bin/check-classes.mjs

@@ -18,11 +18,20 @@
 // are utilities is derived, not listed — anything the build emits that globals.css
 // does not define is Tailwind's.
 //
+// And the reverse: a selector globals.css defines that nothing the build ships
+// references. The shared blocks and chrome render their markup inside
+// wiki-formant while each app styles it, so references are read from the build
+// output, which holds this repo's code, the package's components and bundled
+// libraries alike. A class renamed in the package surfaces here as its old
+// selector going unreferenced. HTML stored in a database is not in the build,
+// so a selector only stored content uses is reported too.
+//
 //   npx check-classes                # exit 1 on any dead token
 //   npx check-classes --warn         # report and exit 0
 //   npx check-classes --compositions # also fail on 3+ inline utilities
+//   npx check-classes --unused       # also fail on unreferenced selectors
 //
-// Run it from the repo root: `.next/static` and `src` are resolved against cwd.
+// Run it from the repo root: `.next` and `src` are resolved against cwd.
 //
 // Needs a build first (npm run build): without one there is nothing to check
 // against, and the script says so and exits 0 rather than failing blind.
@@ -30,7 +39,7 @@ import fs from 'node:fs';
 import path from 'node:path';
 
 const WARN_ONLY = process.argv.includes('--warn');
-const CSS_DIR = '.next/static';
+const STATIC_DIR = '.next/static';
 const SRC_DIR = 'src';
 
 const walk = (dir, ext, out = []) => {
@@ -43,7 +52,7 @@ const walk = (dir, ext, out = []) => {
   return out;
 };
 
-const cssFiles = walk(CSS_DIR, '.css');
+const cssFiles = walk(STATIC_DIR, '.css');
 if (!cssFiles.length) {
   console.log('check-classes: no built CSS under .next/static — run `npm run build` first. Skipping.');
   process.exit(0);
@@ -59,12 +68,18 @@ for (const f of cssFiles) {
 
 // Classes this project defines itself. Everything else the build emitted is a
 // Tailwind utility, which is what makes the composition count derivable rather
-// than a maintained prefix list.
+// than a maintained prefix list. Read from rule preludes only, so a decimal in a
+// value or a class named in a comment is not taken for a selector.
 const globalsFile = walk(SRC_DIR, '.css').find(f => f.endsWith('globals.css'));
 const named = new Set();
 if (globalsFile) {
-  for (const m of fs.readFileSync(globalsFile, 'utf8').matchAll(/\.((?:\\.|[-\w])+)/g)) {
-    named.add(m[1].replace(/\\/g, ''));
+  const css = fs.readFileSync(globalsFile, 'utf8').replace(/\/\*[\s\S]*?\*\//g, '');
+  for (const [, prelude] of css.matchAll(/([^{};]*)\{/g)) {
+    if (prelude.trim().startsWith('@')) continue;
+    for (const m of prelude.matchAll(/\.((?:\\.|[-\w])+)/g)) {
+      const name = m[1].replace(/\\/g, '');
+      if (/^[A-Za-z_-]/.test(name)) named.add(name);
+    }
   }
 }
 
@@ -92,6 +107,7 @@ for (const f of walk(SRC_DIR, '.tsx')) {
 }
 
 const CHECK_COMPOSITIONS = process.argv.includes('--compositions');
+const CHECK_UNUSED = process.argv.includes('--unused');
 
 if (compositions.length) {
   const verb = CHECK_COMPOSITIONS ? 'must be named' : 'should be named (advisory)';
@@ -103,9 +119,30 @@ if (compositions.length) {
   console.error('');
 }
 
+// Every token in the JavaScript the build ships, server and client. A selector
+// is referenced when its name appears whole, or when a prefix of it ending in `-`
+// or `_` does, which is how `editorial-banner-${variant}` is written.
+const shipped = new Set();
+for (const f of [...walk(STATIC_DIR, '.js'), ...walk('.next/server', '.js')]) {
+  for (const [tok] of fs.readFileSync(f, 'utf8').matchAll(/[\w-]+/g)) shipped.add(tok);
+}
+const referenced = name =>
+  shipped.has(name) ||
+  [...name].some((c, i) => i >= 3 && (c === '-' || c === '_') && shipped.has(name.slice(0, i + 1)));
+const unused = [...named].filter(n => !referenced(n)).sort();
+
+if (unused.length) {
+  const verb = CHECK_UNUSED ? 'must be deleted' : 'advisory';
+  console.error(`check-classes: ${unused.length} selector(s) in ${globalsFile} referenced by nothing the build ships (${verb}):\n`);
+  console.error(`  ${unused.join(', ')}\n`);
+  console.error('  Class names inside HTML stored in a database do not count, so check stored content before deleting one.\n');
+}
+
+const advisoryFailed = (CHECK_COMPOSITIONS && compositions.length > 0) || (CHECK_UNUSED && unused.length > 0);
+
 if (!dead.size) {
   console.log(`check-classes: clean — every className token resolves against ${emitted.size} emitted selectors.`);
-  process.exit(CHECK_COMPOSITIONS && compositions.length && !WARN_ONLY ? 1 : 0);
+  process.exit(advisoryFailed && !WARN_ONLY ? 1 : 0);
 }
 
 console.error(`check-classes: ${dead.size} className token(s) style nothing:\n`);

package/dist/block-views.js

@@ -1,6 +1,6 @@
 'use client';
 import { jsx as _jsx, jsxs as _jsxs, Fragment as _Fragment } from "react/jsx-runtime";
-// block-views.tsx — the block renderers both wikis had written twice.
+// block-views.tsx — the block leaves the wikis share.
 //
 // Behind its own subpath for the reason `react.tsx` is: React is an OPTIONAL
 // peer, so a consumer that only wants the taxonomy or the MCP transport still
@@ -10,13 +10,12 @@ import { jsx as _jsx, jsxs as _jsxs, Fragment as _Fragment } from "react/jsx-run
 // that way (see the Block Model note in the workspace CLAUDE.md) — a closed
 // union is what makes `switch (block.type)` exhaustive, so a new block type is
 // a compile error rather than a silent blank. What is NOT per-repo is what a
-// codeTabs or a linkGrid LOOKS like once you have dispatched to it: those were
-// byte-identical in both repos, down to the class names. So the dispatch stays
-// with the caller and the leaves move here.
+// codeTabs or a linkGrid LOOKS like once you have dispatched to it, down to the
+// class names. So the dispatch stays with the caller and the leaves live here.
 //
-// The class names are NOT props. Like the rail's `wiki-rail__*` tree they are
-// the shared convention both stylesheets already implement, and making them
-// configurable would only let that convention fork again. Everything that
+// The class names are NOT props. They are the shared convention every
+// stylesheet implements, and making them configurable would let that convention
+// fork. Everything that
 // genuinely differs — the prose of a banner, whether references run through an
 // HTML processor, the router's link — arrives as a prop.
 import { Fragment, useState } from 'react';

package/dist/combobox.js

@@ -4,21 +4,12 @@
 // pure, so it can be tested without a DOM, and `react.tsx` is left holding only
 // the hook that calls it.
 //
-// `useTypeahead` already shared the state machine across five surfaces in three
-// wikis. The ARIA did not travel with it, and all five had drifted into
-// different wrongness:
-//
-//   - one put `aria-selected` on a plain `<button>`, which is not a role that
-//     takes it, and gave the container no `role="listbox"` at all;
-//   - one gave the rows `role="option"` but still no listbox, so the options
-//     had no owner;
-//   - two had no roles whatsoever;
-//   - one used a `data-highlighted` attribute, which no assistive technology
-//     reads.
-//
-// None of the five set `aria-activedescendant`, which is the attribute that
-// actually announces the highlighted row as the reader arrows through it. A
-// combobox without it is a text field that silently changes what Enter does.
+// `useTypeahead` shares the state machine; this is the ARIA that goes with it:
+// a `role="listbox"` container that owns `role="option"` rows, `aria-selected`
+// on the option rather than on a plain `<button>`, and `aria-activedescendant`,
+// the attribute that announces the highlighted row as the reader arrows
+// through it. A combobox without it is a text field that silently changes what
+// Enter does.
 /** The id of one option row. Exported because a caller that scrolls the
  *  highlighted row into view has to find it by the same id the input points at. */
 export function optionId(baseId, listKey, index) {

package/dist/conformance.js

@@ -19,8 +19,7 @@ import { DEFAULT_MAX_BATCH, MCP_CORS, MCP_PROTOCOL_VERSION } from './mcp.js';
 /**
  * Does the live preflight carry every token `MCP_CORS` declares for this header?
  *
- * Derived rather than listed: the assertion used to name three headers by hand,
- * so a fourth added to `MCP_CORS` was tested by nobody.
+ * Derived rather than listed, so a header added to `MCP_CORS` is tested too.
  */
 const corsCovers = (res, header) => {
     const live = res.headers.get(header) ?? '';
@@ -306,10 +305,9 @@ export async function annotationChecks(t, opts = {}) {
  */
 export async function payloadBudget(t, calls, maxBytes = 120_000) {
     // Every read-only tool a caller can invoke with no arguments at all, whether
-    // or not the suite thought to name it. This check used to weigh only the
-    // listed calls, which is how a tool taking no parameters and answering with
-    // 3.3 MB — 27× the budget it was exempt from — passed a suite that measured
-    // the four tools beside it. A tool with required arguments still has to be
+    // or not the suite thought to name it, so a no-argument tool answering with
+    // megabytes cannot pass by going unlisted. A tool with required arguments
+    // still has to be
     // listed: the suite is the only thing that knows a valid pair.
     const listed = new Set(calls.map(c => c.name));
     const bare = ((await t.rpc('tools/list')).result?.tools ?? [])

package/dist/crawlers.js

@@ -1,22 +1,16 @@
 // crawlers.ts — one roster of AI crawler tokens, for both surfaces that need it.
 //
-// Every wiki in the workspace kept this list twice: once in the proxy, keyed by
-// user-agent substring, to count an "AI Bot Visit"; and once in `robots.ts`, as
-// the set of agents that get their own group. The two copies were each
-// byte-identical across all three repos — and they were different lists.
+// The proxy counts an "AI Bot Visit" by user-agent substring, and `robots.ts`
+// gives each agent its own group. Both read this one roster.
 //
-// Only one direction of that difference was deliberate. `Applebot-Extended`
+// One difference between the two uses is deliberate. `Applebot-Extended`
 // never fetches a page: it is a robots.txt-only token that Applebot consults
 // before using already-crawled data for AI, so counting it would count nothing.
 // That belongs in robots and not in the matcher, and it is declared here.
 //
-// The other direction was not deliberate. Bytespider, CCBot, cohere-ai,
-// Claude-Web and Meta-ExternalFetcher were matched by every proxy and named by
-// no robots.txt — and a crawler obeys only its most-specific matching group, so
-// an agent with no group of its own falls through to `*` and is granted
-// whatever that grants. The wikis were measuring five crawlers they had never
-// addressed. One roster makes that a property of the data rather than of which
-// file you happened to edit.
+// Every other token appears in both, because a crawler obeys only its
+// most-specific matching group: an agent with no group of its own falls through
+// to `*` and is granted whatever that grants.
 /**
  * Order is significant: `detectAiBot` returns the first token the user agent
  * contains, so a token that is a substring of another must come after it.

package/dist/dom.d.ts

@@ -19,8 +19,7 @@ export interface CopyButtonOptions {
 export declare function addCopyButtons(root: ParentNode, options?: CopyButtonOptions): number;
 /**
  * The one place this origin is written down. It is both the embed host and the
- * allow-list the resize listener checks, and it was previously spelled out at
- * four call sites across the two wikis.
+ * allow-list the resize listener checks.
  */
 export declare const TWITTER_ORIGIN = "https://platform.twitter.com";
 /** The embed iframe's src. `dnt=true` opts the embed out of Twitter's tracking. */

package/dist/dom.js

@@ -55,8 +55,7 @@ export function addCopyButtons(root, options = {}) {
 // ---- twitter embeds ---------------------------------------------------------
 /**
  * The one place this origin is written down. It is both the embed host and the
- * allow-list the resize listener checks, and it was previously spelled out at
- * four call sites across the two wikis.
+ * allow-list the resize listener checks.
  */
 export const TWITTER_ORIGIN = 'https://platform.twitter.com';
 /** The embed iframe's src. `dnt=true` opts the embed out of Twitter's tracking. */

package/dist/editor.d.ts

@@ -5,8 +5,7 @@ import { type ChangeEvent, type RefObject } from 'react';
  *
  * Each of these packages ships a `declare module '@tiptap/core'` block that adds
  * its commands to `ChainedCommands` — `toggleBold`, `insertTable`, `setLink`,
- * `setImage`. A consumer that imported the extensions itself picked those up as
- * a side effect of the import; now that this module owns them, it has to carry
+ * `setImage`. Because this module owns the extensions, it has to carry
  * the augmentation across the package boundary, and a re-exported type is what
  * makes the emitted `.d.ts` load the module that declares it. Without these
  * four lines every `editor.chain().focus().toggleBold()` in every consumer
@@ -16,19 +15,6 @@ export type { StarterKitOptions } from '@tiptap/starter-kit';
 export type { LinkOptions } from '@tiptap/extension-link';
 export type { ImageOptions } from '@tiptap/extension-image';
 export type { TableOptions } from '@tiptap/extension-table';
-/**
- * Reduce pasted HTML to structure plus the three attributes that carry meaning.
- *
- * A paste from a word processor or a web page arrives carrying its whole
- * stylesheet inline. Keeping any of it means the wiki's own typography loses to
- * whatever the author copied from, per paragraph, invisibly — and `style` on a
- * pasted node is also the cheapest way to smuggle a full-bleed overlay into a
- * page body.
- *
- * Browser-only: it parses with `DOMParser`. Called from `transformPastedHTML`,
- * which only ever runs in response to a paste.
- */
-export declare function cleanPastedHtml(html: string): string;
 export interface WikiEditorExtensionOptions {
     /** Empty-document prompt. */
     placeholder?: string;
@@ -42,15 +28,6 @@ export interface WikiEditorExtensionOptions {
      */
     nodes?: readonly AnyExtension[];
 }
-/**
- * The editor's extension set.
- *
- * `codeBlock: false` on StarterKit is load-bearing: the consumer registers its
- * own via `createCodeBlock`, and leaving StarterKit's in place would give the
- * schema two nodes claiming the same name. Headings stop at h2 — the page title
- * is the only h1 a wiki page has.
- */
-export declare function wikiEditorExtensions({ placeholder, nodes, }?: WikiEditorExtensionOptions): AnyExtension[];
 /**
  * Turn a pasted URL into the richest node that fits it, falling back to a bare
  * iframe. Order matters: a YouTube URL is also a valid iframe source, so the

package/dist/editor.js

@@ -4,25 +4,16 @@
 // `tiptap.tsx` holds the custom NODES both wikis needed (iframe, tweet, map,
 // code block, tabs). This holds what sits around them: which extensions are
 // configured how, what a paste is scrubbed down to, how a pasted URL becomes
-// the right embed, and the state a toolbar reads. Those were byte-identical in
-// both repos — the same twelve-entry extension array, the same paste scrubber,
-// the same embed dispatch including the shortened-map async swap.
+// the right embed, and the state a toolbar reads.
 //
-// TWO BUGS ARE FIXED HERE RATHER THAN PROPAGATED, and the reason this file
-// exists at all is that each repo had exactly one of them:
+// TWO GUARDS HERE ARE LOAD-BEARING:
 //
-//   1. `onChangeRef.current = onChange` was written DURING render in one copy.
-//      A ref mutated mid-render can tear under concurrent rendering. It is
-//      written in an effect here, and only read from events and timeouts, which
-//      run later.
-//   2. The other copy had no `onBlur`. The change is debounced 150ms, and
-//      clicking Save blurs the editor before the click lands — so the final
-//      keystroke of every edit that ended in a click was dropped. Blur flushes
-//      the pending debounce.
-//
-// Neither repo was "behind": each had shipped the fix the other lacked, which
-// is the drift that costs the most, because neither file looks like the one to
-// fix.
+//   1. `onChangeRef.current = onChange` is written in an effect, never during
+//      render: a ref mutated mid-render can tear under concurrent rendering.
+//      It is only read from events and timeouts, which run later.
+//   2. Blur flushes the pending debounce. The change is debounced 150ms, and
+//      clicking Save blurs the editor before the click lands, so without the
+//      flush the final keystroke of an edit that ends in a click is dropped.
 //
 // Every @tiptap package here is an OPTIONAL PEER. A consumer that only wants
 // the taxonomy or the MCP transport installs none of them.
@@ -50,7 +41,7 @@ import { toMapEmbedUrl } from './maps.js';
  * Browser-only: it parses with `DOMParser`. Called from `transformPastedHTML`,
  * which only ever runs in response to a paste.
  */
-export function cleanPastedHtml(html) {
+function cleanPastedHtml(html) {
     const doc = new DOMParser().parseFromString(html, 'text/html');
     doc.querySelectorAll('style, script, meta, link, svg, canvas, noscript').forEach(el => el.remove());
     doc.querySelectorAll('*').forEach(el => {
@@ -72,7 +63,7 @@ export function cleanPastedHtml(html) {
  * schema two nodes claiming the same name. Headings stop at h2 — the page title
  * is the only h1 a wiki page has.
  */
-export function wikiEditorExtensions({ placeholder = '', nodes = [], } = {}) {
+function wikiEditorExtensions({ placeholder = '', nodes = [], } = {}) {
     return [
         StarterKit.configure({ heading: { levels: [2, 3, 4] }, codeBlock: false }),
         TiptapLink.configure({ openOnClick: false, HTMLAttributes: { class: 'link' } }),

package/dist/headings.js

@@ -1,12 +1,6 @@
 // headings.ts — stable ids on a wiki page's headings, and the list a table of
 // contents is built from.
 //
-// Two of the three wikis had already written this out (caper's `injectHeadingIds`,
-// radix-wiki's heading branch in `processHtml`), down to byte-identical
-// `stripTags` and `getAttr` helpers — caper's file says "ported in spirit from
-// radix-wiki" at the top, which is the drift admitting itself. What they had
-// drifted on is below.
-//
 // The slug rule is a parameter, not a decision this module makes. A heading id
 // is a live URL: readers link to `#the-shape-of-a-code`, and so does the page's
 // own permalink anchor. Unifying two slug rules would silently move every
@@ -15,8 +9,7 @@
 //
 // Deduping, by contrast, is not a choice: two headings with the same text
 // otherwise mint the same id twice and every link to the second one lands on
-// the first. That was already a bug in the copy that lacked it, so this always
-// dedupes.
+// the first, so this always dedupes.
 import { getAttr, stripTags } from './html.js';
 /** The default slug rule: lowercase words joined by hyphens. */
 export function slugifyHeading(text) {

package/dist/link-check.js

@@ -1,18 +1,15 @@
-// link-check.ts — the dead-link probe both wikis' sweep scripts had written.
+// link-check.ts — the dead-link probe wiki sweep scripts share.
 //
 // Node-only (fetch, AbortSignal, URL). No framework, no database: what a
 // checker does with the verdicts — which pages to walk, what counts as an
 // internal path, how to report — stays with the caller, because that is the
 // half that is genuinely per-wiki.
 //
-// EVERY GUARD BELOW WAS PAID FOR BY A FALSE POSITIVE, and the two copies had
-// each learned a different half of the lesson. One knew that npmjs.com 403s
-// scripted requests, that an expired certificate is not a dead host, and that a
-// YouTube /embed/ URL answers 200 for a deleted video. The other knew that a
-// connect refusal is usually concurrency rather than death, and that
-// serialising per hostname is what fixes it. Neither copy was behind. A sweep
-// running either one alone strips good citations for reasons the other repo had
-// already written down — which is the entire argument for this file.
+// EVERY GUARD BELOW WAS PAID FOR BY A FALSE POSITIVE. npmjs.com 403s scripted
+// requests, an expired certificate is not a dead host, a YouTube /embed/ URL
+// answers 200 for a deleted video, and a connect refusal is usually concurrency
+// rather than death, which serialising per hostname fixes. A sweep missing any
+// one of these strips good citations.
 import { stripTags } from './html.js';
 const DEFAULTS = { timeoutMs: 12_000, slowTimeoutMs: 40_000 };
 /**

package/dist/maps.d.ts

@@ -3,8 +3,6 @@ export interface MapCoords {
     lon: number;
     zoom?: number | undefined;
 }
-/** A plain embed URL for a coordinate pair. */
-export declare function mapsEmbedUrl(lat: number, lon: number, zoom?: number): string;
 /**
  * Dig a coordinate pair out of a maps URL. Four shapes in descending
  * specificity: the `@lat,lon,zoom` path segment, a `/search/lat,lon`, the

package/dist/maps.js

@@ -4,7 +4,7 @@
 // pure string work over Google and Apple Maps URL shapes, with no framework or
 // database in it, which is why neither copy had a reason to diverge.
 /** A plain embed URL for a coordinate pair. */
-export function mapsEmbedUrl(lat, lon, zoom = 15) {
+function mapsEmbedUrl(lat, lon, zoom = 15) {
     return `https://maps.google.com/maps?q=${lat},${lon}&z=${zoom}&output=embed`;
 }
 /**

package/dist/mcp.d.ts

@@ -11,10 +11,6 @@ export declare const MCP_PROTOCOL_VERSIONS: readonly ["2025-06-18", "2025-03-26"
 export type McpProtocolVersion = (typeof MCP_PROTOCOL_VERSIONS)[number];
 /** The newest version spoken here, and what an unrecognised ask falls back to. */
 export declare const MCP_PROTOCOL_VERSION: McpProtocolVersion;
-/** Echo the client's version when it is one we speak, else offer the newest. */
-export declare function negotiateProtocol(requested: unknown): McpProtocolVersion;
-/** The version a post-initialize request is operating under. */
-export declare function requestProtocol(request: Request): McpProtocolVersion;
 import { type RateLimitOptions } from './rate-limit.js';
 export type ToolParam = {
     type: 'string' | 'number' | 'boolean' | 'array' | 'object';

package/dist/mcp.js

@@ -28,11 +28,11 @@ export const MCP_PROTOCOL_VERSION = MCP_PROTOCOL_VERSIONS[0];
 const ASSUMED_VERSION = '2025-03-26';
 const speaks = (v) => MCP_PROTOCOL_VERSIONS.includes(v);
 /** Echo the client's version when it is one we speak, else offer the newest. */
-export function negotiateProtocol(requested) {
+function negotiateProtocol(requested) {
     return speaks(requested) ? requested : MCP_PROTOCOL_VERSION;
 }
 /** The version a post-initialize request is operating under. */
-export function requestProtocol(request) {
+function requestProtocol(request) {
     const header = request.headers.get('mcp-protocol-version');
     return speaks(header) ? header : ASSUMED_VERSION;
 }
@@ -143,9 +143,7 @@ function methodsFor(config) {
         ...BASE_METHODS,
         // The list methods answer whether or not anything is registered: an empty
         // list is a better answer to a client that asked than a -32601 it has to
-        // interpret. This enumeration used to omit them while the dispatch below
-        // answered them, so the error message contradicted the server describing
-        // itself.
+        // interpret.
         'resources/list',
         'resources/templates/list',
         'prompts/list',
@@ -286,13 +284,12 @@ async function handleRpc(req, config, dispatch) {
                 try {
                     const data = await tool.handler(args, ctx);
                     const text = typeof data === 'string' ? data : JSON.stringify(data, null, 2);
-                    // Every object answer, not only the schema-bearing ones. Gating this
-                    // on `outputSchema` meant that across four live servers and thirty-two
-                    // tools — every one of them returning JSON — not a single result ever
-                    // carried `structuredContent`, and every agent parsed prose to reach
-                    // data the server already had in hand. A declared `outputSchema` is
-                    // still the stronger contract (a client validates against it); it is
-                    // no longer the price of admission. The text block stays regardless:
+                    // Every object answer, not only the schema-bearing ones. Gated on
+                    // `outputSchema`, a JSON-returning tool without one would carry no
+                    // `structuredContent`, and agents would parse prose to reach data the
+                    // server has in hand. A declared `outputSchema` is the stronger
+                    // contract (a client validates against it), not the price of
+                    // admission. The text block stays regardless:
                     // the spec asks for the serialised twin, and a client that reads only
                     // content still has to be able to read the answer.
                     const structured = data !== null && typeof data === 'object' && !Array.isArray(data)

package/dist/pagination.d.ts

@@ -7,8 +7,6 @@ export interface PaginatedResponse<T> extends Pagination {
     total: number;
     totalPages: number;
 }
-export declare const MAX_PAGE_SIZE = 100;
-export declare const DEFAULT_PAGE_SIZE = 20;
 /**
  * `page` clamped to ≥1, `pageSize` clamped to 1–`max`. Never trust either.
  *
@@ -55,14 +53,12 @@ export declare function toOffset({ page, pageSize }: Pagination): {
  * The ordering is the caller's, deliberately — it is the one thing here that is
  * never portable. A wiki's sequence is its section's configured sort, a
  * knowledge base's is a taxonomy walk, and a company log's is `updatedAt` desc.
- * What both wikis had written twice is this scan, not the sort.
  *
  * `null` on both sides when the page is not in the list, so a page reached by a
  * URL its own section does not list renders no nav rather than a wrong one.
  *
- * No query. Both callers already hold the ordered siblings for something else —
- * a related-pages panel, a section listing — and the two indexed lookups the
- * neighbours used to cost were the reason one wiki dropped the control.
+ * No query. Callers already hold the ordered siblings for something else, a
+ * related-pages panel or a section listing, so the neighbours cost no lookups.
  */
 export declare function adjacentPages<T>(ordered: readonly T[], isCurrent: (page: T) => boolean): {
     prev: T | null;

package/dist/pagination.js

@@ -3,8 +3,8 @@
 // Forked three ways once: a re-typed clamp that dropped `totalPages`, and an
 // offset redone by hand in raw SQL. The response shape is the contract a client
 // codes against, so reshaping it per repo is a breaking change nobody declared.
-export const MAX_PAGE_SIZE = 100;
-export const DEFAULT_PAGE_SIZE = 20;
+const MAX_PAGE_SIZE = 100;
+const DEFAULT_PAGE_SIZE = 20;
 /**
  * `page` clamped to ≥1, `pageSize` clamped to 1–`max`. Never trust either.
  *
@@ -62,14 +62,12 @@ export function toOffset({ page, pageSize }) {
  * The ordering is the caller's, deliberately — it is the one thing here that is
  * never portable. A wiki's sequence is its section's configured sort, a
  * knowledge base's is a taxonomy walk, and a company log's is `updatedAt` desc.
- * What both wikis had written twice is this scan, not the sort.
  *
  * `null` on both sides when the page is not in the list, so a page reached by a
  * URL its own section does not list renders no nav rather than a wrong one.
  *
- * No query. Both callers already hold the ordered siblings for something else —
- * a related-pages panel, a section listing — and the two indexed lookups the
- * neighbours used to cost were the reason one wiki dropped the control.
+ * No query. Callers already hold the ordered siblings for something else, a
+ * related-pages panel or a section listing, so the neighbours cost no lookups.
  */
 export function adjacentPages(ordered, isCurrent) {
     const i = ordered.findIndex(isCurrent);

package/dist/rate-limit.d.ts

@@ -69,10 +69,9 @@ export declare function resetRateLimits(): void;
  * `.well-known/mcp.json`, the OpenAPI spec, agents.md, llms.txt and the
  * `initialize` instructions all quote this, so the endpoint enforces exactly
  * what the documents claim. It is a cross-surface contract, which is why it
- * lives here rather than three times over: it had already drifted to 200 on one
- * surface with nothing recorded about why, and that is the state that makes a
- * number impossible to change safely later — nobody can tell a considered
- * difference from a stale one.
+ * lives here rather than three times over. A second copy is how a number
+ * becomes impossible to change safely: nobody can tell a considered difference
+ * from a stale one.
  *
  * A surface with a genuine reason to differ passes its own `RateLimitOptions`.
  * What it must not do is restate this one.

package/dist/rate-limit.js

@@ -117,10 +117,9 @@ export function resetRateLimits() {
  * `.well-known/mcp.json`, the OpenAPI spec, agents.md, llms.txt and the
  * `initialize` instructions all quote this, so the endpoint enforces exactly
  * what the documents claim. It is a cross-surface contract, which is why it
- * lives here rather than three times over: it had already drifted to 200 on one
- * surface with nothing recorded about why, and that is the state that makes a
- * number impossible to change safely later — nobody can tell a considered
- * difference from a stale one.
+ * lives here rather than three times over. A second copy is how a number
+ * becomes impossible to change safely: nobody can tell a considered difference
+ * from a stale one.
  *
  * A surface with a genuine reason to differ passes its own `RateLimitOptions`.
  * What it must not do is restate this one.

package/dist/react-server.d.ts

@@ -54,7 +54,7 @@ export interface FacetBarProps {
  * dropping the active facets — and the A–Z row leads with the reset control.
  *
  * `aria-current`, not `aria-pressed`: a link is not a toggle button and does not
- * take that attribute. Two of the three copies this replaces had it wrong.
+ * take that attribute.
  */
 export declare function FacetBar({ link: Link, facets, letters, alphaLabel, classNames, }: FacetBarProps): import("react").JSX.Element | null;
 export interface BreadcrumbItem {
@@ -114,7 +114,7 @@ export declare function Breadcrumbs({ items, base, className, link: Link, lastAs
  * The standard page-top row: the trail, plus optional right-aligned actions.
  *
  * The column it sits in is the one its route declares — the row reads the
- * page's own max-width by inheritance, so a trail can no longer disagree with
+ * page's own max-width by inheritance, so a trail cannot disagree with
  * the content it titles.
  */
 export declare function BreadcrumbsRow({ actions, className, ...props }: BreadcrumbsProps & {
@@ -146,15 +146,11 @@ export interface PageNavProps {
  * lateral links do not cover.
  *
  * Ordering is entirely the caller's; pair this with `adjacentPages` from
- * `wiki-formant/pagination` over a list you already hold. Both wikis had this
- * markup and had already drifted on the parts that matter rather than the parts
- * that show: one carried `rel="prev"`/`rel="next"` and an `aria-label` and the
- * other carried neither, and the one without expressed its right-hand alignment
- * as two inline utilities instead of the modifier its own stylesheet defines.
+ * `wiki-formant/pagination` over a list you already hold.
  *
- * The `page-nav__*` class names are NOT props, for the reason `WikiRail`'s are
- * not: they are the convention both stylesheets already implement, and making
- * them configurable is how a convention forks. The empty `<div>` holds the
- * first article's left column so the next link stays in the right one.
+ * The `page-nav__*` class names are NOT props: they are the convention every
+ * stylesheet implements, and making them configurable is how a convention
+ * forks. The empty `<div>` holds the first article's left column so the next
+ * link stays in the right one.
  */
 export declare function PageNav({ prev, next, link: Link, label, prevLabel, nextLabel, prevGlyph, nextGlyph, }: PageNavProps): import("react").JSX.Element | null;

package/dist/react-server.js

@@ -34,7 +34,7 @@ export const Anchor = ({ href, className, children }) => _jsx("a", { href: href,
  * dropping the active facets — and the A–Z row leads with the reset control.
  *
  * `aria-current`, not `aria-pressed`: a link is not a toggle button and does not
- * take that attribute. Two of the three copies this replaces had it wrong.
+ * take that attribute.
  */
 export function FacetBar({ link: Link, facets, letters, alphaLabel = 'A–Z', classNames = {}, }) {
     if (!facets.length && !letters.length)
@@ -85,7 +85,7 @@ export function Breadcrumbs({ items, base, className = '', link: Link = Anchor,
  * The standard page-top row: the trail, plus optional right-aligned actions.
  *
  * The column it sits in is the one its route declares — the row reads the
- * page's own max-width by inheritance, so a trail can no longer disagree with
+ * page's own max-width by inheritance, so a trail cannot disagree with
  * the content it titles.
  */
 export function BreadcrumbsRow({ actions, className = '', ...props }) {
@@ -96,16 +96,12 @@ export function BreadcrumbsRow({ actions, className = '', ...props }) {
  * lateral links do not cover.
  *
  * Ordering is entirely the caller's; pair this with `adjacentPages` from
- * `wiki-formant/pagination` over a list you already hold. Both wikis had this
- * markup and had already drifted on the parts that matter rather than the parts
- * that show: one carried `rel="prev"`/`rel="next"` and an `aria-label` and the
- * other carried neither, and the one without expressed its right-hand alignment
- * as two inline utilities instead of the modifier its own stylesheet defines.
+ * `wiki-formant/pagination` over a list you already hold.
  *
- * The `page-nav__*` class names are NOT props, for the reason `WikiRail`'s are
- * not: they are the convention both stylesheets already implement, and making
- * them configurable is how a convention forks. The empty `<div>` holds the
- * first article's left column so the next link stays in the right one.
+ * The `page-nav__*` class names are NOT props: they are the convention every
+ * stylesheet implements, and making them configurable is how a convention
+ * forks. The empty `<div>` holds the first article's left column so the next
+ * link stays in the right one.
  */
 export function PageNav({ prev, next, link: Link = Anchor, label = 'Article navigation', prevLabel = 'Previous', nextLabel = 'Next', prevGlyph = '\u2190', nextGlyph = '\u2192', }) {
     if (!prev && !next)

package/dist/react.d.ts

@@ -22,14 +22,6 @@ export interface SidebarState {
      */
     ready: boolean;
 }
-/**
- * Collapse state for a wiki rail: remembered across loads, defaulted from the
- * viewport only when the reader has never chosen.
- *
- * The reader's choice outranks the breakpoint. Someone who collapses the rail
- * on a laptop and then narrows the window has still collapsed the rail.
- */
-export declare function useCollapsibleSidebar(options?: SidebarOptions): SidebarState;
 export interface SidebarProviderProps extends SidebarOptions {
     children: ReactNode;
 }
@@ -286,8 +278,7 @@ export declare class ErrorBoundary extends Component<{
     children: ReactNode;
     /**
      * `error` is passed as well as `retry` because a fallback that cannot see
-     * what failed can only say "something went wrong" — which is what one of
-     * the copies this replaced said, while the other had the message and used it.
+     * what failed can only say "something went wrong".
      */
     fallback: (retry: () => void, error: unknown) => ReactNode;
     onError?: (error: unknown) => void;

package/dist/react.js

@@ -47,7 +47,7 @@ const readStored = (key) => {
  * The reader's choice outranks the breakpoint. Someone who collapses the rail
  * on a laptop and then narrows the window has still collapsed the rail.
  */
-export function useCollapsibleSidebar(options = {}) {
+function useCollapsibleSidebar(options = {}) {
     const { storageKey = 'wiki:sidebar', breakpoint = 1024 } = options;
     // Start open on the server and on the first client paint. SSR has no viewport
     // and no storage, so any other guess is a guaranteed mismatch on some loads.

package/dist/revisions.d.ts

@@ -54,15 +54,6 @@ interface Located<B> {
 }
 /** Every block in the tree, flattened, each with the path that addresses it. */
 export declare function extractBlocks<B>(blocks: readonly B[], containers: (block: B) => BlockGroup<B>[] | null, basePath?: string): Located<B>[];
-/**
- * Which scalar fields differ. Nested block arrays are skipped: they are walked
- * as their own entries, and comparing them here would report a container as
- * modified every time anything inside it moved.
- */
-export declare function diffAttributes<B extends DiffBlock>(oldBlock: B, newBlock: B, containers: (block: B) => BlockGroup<B>[] | null): Record<string, {
-    from: unknown;
-    to: unknown;
-}> | undefined;
 /**
  * Blocks matched by id, so a block that moved is reported as moved rather than
  * as one removal and one addition.

package/dist/revisions.js

@@ -1,17 +1,9 @@
 // revisions.ts — what changed between two versions of a page.
 //
 // The semver lives next door in `versioning.ts`; this is the walk that decides
-// which bump to ask for. Both wikis had written it, and `extractBlocks` was
-// byte-identical between the two copies.
-//
-// They differed in what each had learned since. One grew a leaf-level diff, a
-// second changed-flag for the page's banner, and a `patch` classification for
-// when only that flag moved. The other grew none of those and instead dropped
-// twenty-five lines the first still carries: two Maps keyed by a recursive
-// JSON.stringify of every block, built on every save and never read once.
-// Matching is by id and always was.
-//
-// This is the union, minus the dead half.
+// which bump to ask for. It carries a leaf-level diff, a changed-flag for the
+// page's banner, and a `patch` classification for when only that flag moved.
+// Matching is by id.
 import { incrementVersion, parseVersion } from './versioning.js';
 /** Every block in the tree, flattened, each with the path that addresses it. */
 export function extractBlocks(blocks, containers, basePath = 'root') {
@@ -30,7 +22,7 @@ export function extractBlocks(blocks, containers, basePath = 'root') {
  * as their own entries, and comparing them here would report a container as
  * modified every time anything inside it moved.
  */
-export function diffAttributes(oldBlock, newBlock, containers) {
+function diffAttributes(oldBlock, newBlock, containers) {
     const diffs = {};
     // Derived from these two blocks rather than from the tree, so a container
     // nested inside another container is still exempted. Deriving it once from

package/dist/rola.js

@@ -1,17 +1,11 @@
 // rola.ts — Radix On-Ledger Authentication: challenge, proof, session.
 //
-// Two Radix wikis had written this file, and the copies were 94% identical — the
-// whole difference was a cookie name, plus the half radix-wiki had learned and
-// miow had not: persona (identity_*) proofs, which miow rejected because it
-// passed `type: 'account'` unconditionally, and the error logging that makes a
-// failed verification diagnosable at all.
+// Parameterised on the two things a second wiki would differ in: the cookie
+// name and its dApp identity. It verifies persona (identity_*) proofs as well
+// as account proofs, and logs a failed verification so it is diagnosable.
 //
-// This is radix-wiki's version, parameterised on the two things a second wiki
-// would actually differ in: the cookie name and its dApp identity.
-//
-// **One consumer, as of Sep 2026.** miow is retired, so the second wiki this was
-// parameterised for no longer exists; caper's wallet auth never used this stack
-// and acuiq gates only its wiki editor, on a shared secret. Keep it — the
+// **One consumer.** caper's wallet auth never used this stack and acuiq gates
+// only its wiki editor, on a shared secret. Keep it — the
 // persona-proof fix and the error logging are worth not losing, and the ports
 // below are what make it reusable at all — but do not mistake it for a proven
 // shared abstraction. It is radix-wiki's auth that happens to live in a package.

package/dist/taxonomy.d.ts

@@ -44,12 +44,11 @@ export interface RelatedRanking<T> {
  * value is precisely a set the category view already filters and counts, so the
  * row is the way into that set rather than dead text.
  *
- * Rows, not markup: the three wikis this was lifted from render the same
- * selection three ways (an HTML `<table>` string folded into a block, a React
- * `<aside>`, a markdown twin), and they differ only in how a value is
- * *formatted* — a `url` gets an external link here, a shortened display there.
- * What they had all rebuilt, and had already begun to disagree about, is which
- * keys appear and where each one links.
+ * Rows, not markup: wikis render the same selection differently (an HTML
+ * `<table>` string folded into a block, a React `<aside>`, a markdown twin) and
+ * differ only in how a value is *formatted*: a `url` gets an external link
+ * here, a shortened display there. Which keys appear and where each one links
+ * is what they share.
  */
 export interface MetadataRow extends MetadataKeyDefinition {
     value: string;
@@ -119,7 +118,6 @@ export interface TaxonomyConfig {
 export declare function hrefBuilder(prefix?: string): (tagPath: string, state: CategoryState) => string;
 /** Categories mounted at the root. */
 export declare const defaultHref: (tagPath: string, state: CategoryState) => string;
-export declare const DEFAULT_ALPHA_INDEX_MIN_PAGES = 40;
 /** Bucket for titles that don't start with a letter (numerals, `$CAPER`). */
 export declare function firstLetter(title: string): string;
 /** Adding a filter already active removes it, so every chip is its own off-switch. */

package/dist/taxonomy.js

@@ -36,7 +36,7 @@ export function hrefBuilder(prefix = '') {
 }
 /** Categories mounted at the root. */
 export const defaultHref = hrefBuilder();
-export const DEFAULT_ALPHA_INDEX_MIN_PAGES = 40;
+const DEFAULT_ALPHA_INDEX_MIN_PAGES = 40;
 const metaValue = (page, key) => (page.metadata?.[key] ?? '').trim();
 /** Bucket for titles that don't start with a letter (numerals, `$CAPER`). */
 export function firstLetter(title) {

package/dist/text.d.ts

@@ -33,15 +33,6 @@ export declare function bannerToText(label: string, text?: string | null): strin
 export declare function codeTabsToText(tabs: readonly CodeTab[]): string;
 /** A numbered reference list, or `''` when there are none. */
 export declare function referencesToText(items: readonly ReferenceItem[]): string;
-/**
- * Every `text` value at any depth of a block tree, in document order.
- *
- * Deliberately NOT the typed extractor above: that walks a switch and formats
- * for reading (labels, bullets, reference numbering), so it can surface text a
- * search index never matched and miss text it did. A snippet claiming to show
- * why a row matched has to read the same bytes the match was made against.
- */
-export declare function collectText(node: unknown, out?: string[]): string[];
 /**
  * The passage that matched `query`, not the opening of the page.
  *

package/dist/text.js

@@ -73,7 +73,7 @@ export function referencesToText(items) {
  * search index never matched and miss text it did. A snippet claiming to show
  * why a row matched has to read the same bytes the match was made against.
  */
-export function collectText(node, out = []) {
+function collectText(node, out = []) {
     if (Array.isArray(node)) {
         for (const item of node)
             collectText(item, out);

package/dist/tiptap.js

@@ -1,17 +1,12 @@
 'use client';
 import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
-// tiptap.tsx — the custom editor nodes both wikis had written twice.
+// tiptap.tsx — the custom editor nodes the wikis share.
 //
 // Behind its own subpath for the same reason `react.tsx` is: the four
 // `@tiptap/*` packages are OPTIONAL peer dependencies, so a consumer that only
 // wants the taxonomy or the MCP transport still installs a package with no
 // runtime dependencies at all.
 //
-// The two copies had drifted in both directions — one had grown tabs the other
-// lacked, the other had extracted the Twitter helper the first still wrote out
-// three times — which is the shape of drift that costs the most: neither copy
-// is behind, so neither looks like the one to fix.
-//
 // What is shared is the node schema and its behaviour, never appearance. Class
 // names and icons are injected, which is what lets one wiki keep `text-jupiter`
 // and the other `text-accent` without either forking the node. It also keeps
@@ -64,7 +59,7 @@ export const YouTube = TiptapYoutube.extend({
 function TwitterEmbedView({ node }) {
     const containerRef = useRef(null);
     // The embed posts its measured height back; `onTweetResize` owns the origin
-    // check, which is the part that was written out at four call sites.
+    // check.
     useEffect(() => onTweetResize(height => {
         const iframe = containerRef.current?.querySelector('iframe');
         if (iframe)

package/dist/versioning.js

@@ -2,7 +2,7 @@
 //
 // The block-diff half stays in the app: it has to walk a block tree, and every
 // project owns its own type set. What travels is the version arithmetic and the
-// rule for choosing a bump, which had drifted into a per-repo string split.
+// rule for choosing a bump.
 /** Tolerant of null, empty and malformed input — a page always has a version. */
 export function parseVersion(version) {
     if (!version)

package/dist/well-known.d.ts

@@ -55,12 +55,6 @@ export interface AgentCardLicense {
     /** What the licence covers, e.g. `'content'`. */
     scope?: string;
 }
-/**
- * The A2A revision these cards are written to. Required since v0.3 — a card
- * without it is not a card a spec-current client will accept, and all three
- * origins here were serving one.
- */
-export declare const A2A_PROTOCOL_VERSION = "0.3.0";
 export interface AgentCardConfig {
     name: string;
     description: string;

package/dist/well-known.js

@@ -61,7 +61,7 @@ export function skillsFromTools(tools) {
  * without it is not a card a spec-current client will accept, and all three
  * origins here were serving one.
  */
-export const A2A_PROTOCOL_VERSION = '0.3.0';
+const A2A_PROTOCOL_VERSION = '0.3.0';
 /**
  * An A2A Agent Card. Serve the same object at both `/.well-known/agent.json`
  * and `/.well-known/agent-card.json`: v0.3 renamed the path and defined no

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wiki-formant",
-  "version": "0.17.1",
+  "version": "0.18.0",
   "description": "The portable half of a wiki: derived taxonomy and facet controls, a version-negotiating MCP transport, markdown twins, block rendering, a rich-text editor engine, and conditional-GET plumbing.",
   "type": "module",
   "license": "MIT",