fixup! docs: goal tree and rules track the 1c cache

1e: the fill is driven from the webkey page over Cap'n Web.

Generated-by: Claude Opus 5.5

capsite-checklist.md

@@ -48,8 +48,10 @@ narrative.
         filters"); done when they're unskipped and green.
 
   - [x] **1e. Fill job: a button that grabs every page** into a cache
-        (`POST /_fill`; `startFill`/`fillStatus`/`stopFill` in
-        `diigo-cache/src/cache.ts`; `tests/fill.test.ts`).
+        from the webkey page `/cache/#<key>`, which trades the key for a
+        capability over Cap'n Web (`diigo-cache/src/api.ts`;
+        `startFill`/`fillStatus`/`stopFill` in `src/cache.ts`;
+        `tests/fill.test.ts`).
 
   - [ ] **2. madmode collects real bookmarks via the webapp cookie path**
         (the API-key path is dead: [evidence in the notes](capsite-notes.md#where-the-diigo-credentials-go))
@@ -138,7 +140,8 @@ to every goal in this tree.
   native-plugin wiring details
 - [docs/webkeys.md](docs/webkeys.md) — the Waterken URL-capability
   pattern, abstracted from the E-on-Java sources (bearer secrets,
-  YURL32, secret≠address); the reason ids never ride URLs
+  YURL32, secret≠address); the reason ids ride only fragments and POST
+  bodies
 - [the mm-diigo diigo-bak scripts](https://github.com/dckc/mm-diigo) —
   provenance of the fluent client and dump generator (`projects/diigo-bak/`:
   WebApp.js, diigo-dump.mjs, diigo-interact.mjs; mm-diigo commit 7dbb367,