@panaversity/ksor 0.0.33 → 0.0.34

package/CHANGELOG.md

@@ -1,5 +1,29 @@
 # @panaversity/ksor
 
+## 0.0.34
+
+### Patch Changes
+
+- e18ea08: The second site shell is retired (decision 9 revision, owner). Nothing an
+  adopter runs changes: `ksor init` has always emitted Fumadocs and never offered
+  a selector.
+
+  The proof did its job. It was built to answer whether the shell is really a slot
+  or whether the surface contract was just a description of what Fumadocs happens
+  to do, and it kept that contract honest through the visibility model,
+  attachments and the staging lock. What it costs now exceeds that: every surface
+  the record grows — quizzes, decks, slides, code tabs — has to be built twice or
+  the conformance suite goes red, and the second build is one nobody ships.
+  Maintaining a shell no adopter runs, to prove a property no adopter exercises,
+  is the "code is liability" test failing.
+
+  The five-clause surface contract survives unchanged and is still asserted,
+  against one implementation. The other clauses decision 9 always leaned on —
+  adopter ownership of `system/site`, registry-distributed shells later — are what
+  carry replaceability now. The swap recipe lives in git history; an adopter
+  actually swapping a shell restores the property as something live rather than
+  hypothetical.
+
 ## 0.0.33
 
 ### Patch Changes

package/docs/index.md

@@ -68,9 +68,9 @@ instance declares an `audiences:` model, documents may carry a
 `visibility:` key and per-audience builds (`KSOR_AUDIENCE=<tier> pnpm
 build`) stage only what that tier may see — publication, not authorship:
 anyone who can clone reads everything. The site shell
-at `system/site/` is replaceable behind a five-clause surface contract; a
-Docusaurus conformance shell lives in the ksor repository under
-`workbench/shells/docusaurus/` with its swap recipe.
+at `system/site/` is replaceable behind a five-clause surface contract — the
+shell is a slot, and the contract (render the record, `llms.txt`, per-page md
+artifacts, browser smoke, no authored content) is what a replacement must meet.
 
 ## Where truth lives
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@panaversity/ksor",
-  "version": "0.0.33",
+  "version": "0.0.34",
   "description": "Knowledge System of Record — compile governed markdown into a static site for people and an MCP server for AI agents, with citations and measured abstention.",
   "keywords": [
     "abstention",

package/templates/scaffold/AGENTS.md

@@ -708,8 +708,8 @@ You own `system/site/` outright — these are the seams, cheapest first:
   documentation shell around it stay one palette.
 - **Anything deeper** — edit the site like the Next.js app it is; the only
   rule that survives customization is critical rule 1. The whole shell is
-  replaceable behind a five-clause contract (a themed Docusaurus shell with
-  a swap recipe lives in the ksor repository under `workbench/shells/`).
+  replaceable behind a five-clause contract: render the record, `llms.txt`,
+  per-page md artifacts, browser smoke, and no authored content.
 
 ## What this project owns