@@ -103,9 +103,7 @@ actively depends on them.** Its `/pr/bs` endpoint builds a JSON "bookshelf" payl
 and renders it with the Pebble template engine. More generally, any `Content` row with a non-zero
 `templateId` gets its stored (decompressed) content run through the matching row in `Templates` as
 a Pebble template before being served. This is a real, current feature of the shipped server, not
-a placeholder. Note this repo does now write to `Templates`: `populate_db.py` upserts `page.peb`
-and `nav.peb` there (and points every page it inserts at them via `templateId`), so the table is
-no longer read-only from this side.
+a placeholder.
 
 In a database whose newest `DocumentationDatabaseVersion` row declares major 3 or later, every
 `Templates` row is stored Brotli-compressed against the shared dictionary, with no per-row marker
@@ -114,24 +112,24 @@ plain templates. `remint_dictionary.py` and `verify_remint_dictionary.py` read t
 the app does: from major 3 on they sample, recompress and verify the templates together with the
 `Content` rows, and below it they leave the templates exactly as stored.
 
-**Nothing that currently builds or writes to the database in this repository knows about any of
-that — and that's expected.** `Templates`/`Bookshelf`/`BookCategories` are populated by a separate
-plugin system, not by anything in this repo: App Dev For All supports plugins that write into the
-documentation database, including the bookshelf feature specifically —
-[appdevforall/bookshelf-plugin](https://github.com/appdevforall/bookshelf-plugin). So the absence
-of any `Templates`/`Bookshelf`/`BookCategories` handling here is not a gap to fill; it's out of
-scope for this repo. (A repo-wide search for `Templates`, `Bookshelf`, `BookCategories`, or `PUCC`
-turns up zero matches outside `WebServer.kt` itself, which is consistent with that division of
-responsibility. `templateId` itself is a different story - `populate_db.py` and
-`insert_optimized_media.py` both read/write it directly, since it's a plain column on `Content`
-they populate; it's only the `Templates` table and the plugin system that reference it that stay
-out of scope.) Concretely, relative to the schema above:
+**This repo writes `Templates`, but not `Bookshelf` or `BookCategories`.** `populate_db.py`
+(`page.peb`, `nav.peb`), `sync_javadoc_json_to_db.py` (`javadoc.peb`) and `load_android_json_db.py`
+(the `android-*.peb` templates) write rows there and point the pages they write at them via
+`templateId`; `verify_android_json_db.py` reads them; and `remint_dictionary.py` and
+`verify_remint_dictionary.py` recompress and compare them from 3.0.0 on (above).
+`insert_optimized_media.py` reads and writes `templateId` too.
+`Bookshelf` and `BookCategories` come from App Dev For All's plugin system, which writes into the
+documentation database - the bookshelf feature from
+[appdevforall/bookshelf-plugin](https://github.com/appdevforall/bookshelf-plugin), now archived on
+GitHub. Nothing here writes them, except that `Content`'s `AddBook` trigger adds a `Bookshelf` row
+for each `.pdf` path inserted (see `migrate_content_to_dictionary_brotli.py`). Concretely, relative
+to the schema above:
 
 | Piece | What it thinks the schema is | Consequence |
 | --- | --- | --- |
 | `scripts/DocumentationDatabase.py` (used by `scripts/ingest.py`, and hence by `.github/workflows/publish-doc-db.yaml`) | `Content` / `Languages` / `ContentTypes` only, plus an optional `ide_tooltip_table`. Its constructor explicitly **raises `ValueError`** if it opens a DB containing any table outside that whitelist. | **This will refuse to open the current production `documentation.db` at all** — it will list `Tooltips`, `TooltipCategories`, `TooltipButtons`, `TooltipButtonNumbers`, `LastChange`, `Templates`, `BookCategories`, `Bookshelf`, and every `PUCC_*` table as "unexpected." This is the single biggest blocker to reusing this script as-is. |
 | `docdb-studio/SCHEMA.md` / `AGENTS.md` (states the schema is "locked," no migrations) | `Content` (no `templateId`, no `UNIQUE(path)`), `Tooltips`, `TooltipButtons`, `TooltipCategories`, `TooltipButtonNumbers`, `LastChange` (with a *different* shape: `documentationSet`/`changeTime`/`who` — this part does match current), plus a legacy `ide_tooltip_table`. Missing `templateId`, `Templates`, `BookCategories`, `Bookshelf`, `PUCC_*`. | Closest of the three documented schemas to reality, but still out of date. `docdb_studio.py`'s own "never change the schema" policy is itself now stale, since the live schema has already changed underneath it. |
-| `check-tools/README.md`'s embedded schema (and by extension the mental model behind `check-tools/db_health_checker.py`) | `Content` (no `templateId`, no `UNIQUE(path)`), `Tooltips`, `TooltipButtons`, `TooltipCategories`, `TooltipButtonNumbers`, and a *third* variant of `LastChange` (`now`/`who`). No `Templates`/`Bookshelf`/`BookCategories`/`PUCC_*`. | The health checker's required-table check still passes (it only checks that its known tables exist, not that no others do). Since `Templates`/`Bookshelf`/`BookCategories` are out of scope for this repo (see above), this is not being treated as something to fix right now. |
+| `check-tools/README.md`'s embedded schema (and by extension the mental model behind `check-tools/db_health_checker.py`) | `Content` (no `templateId`, no `UNIQUE(path)`), `Tooltips`, `TooltipButtons`, `TooltipCategories`, `TooltipButtonNumbers`, and a *third* variant of `LastChange` (`now`/`who`). No `Templates`/`Bookshelf`/`BookCategories`/`PUCC_*`. | The health checker's required-table check still passes (it only checks that its known tables exist, not that no others do). Since `Bookshelf`/`BookCategories` are written outside this repo (see above) and check-tools reads no `Templates`, this is not being treated as something to fix right now. |
 
 There also appear to be **two unrelated tooltip storage formats** in this repo's history, and it's
 worth being deliberate about which one is current: