feat(permissions): add app.certified.signature.proof to the Certified set

PR #219 (signature support, HYPER-181) has now merged to main, adding the
app.certified.signature.proof record lexicon. This was the documented follow-up:
app.certified.authWrite must enumerate every app.certified.* record collection,
so the newly-landed collection has to be added or it is not grantable via the
published set.

Add it (the set now lists all 9 app.certified.* records, verified identical to
the type:"record" defs on disk), sync the JSONC example in the design doc, and
drop the now-resolved "Known pending update (#219)" note from the Maintenance
section. SCHEMAS.md regenerated. npm run check passes (182 tests).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: aspiers

SCHEMAS.md

@@ -734,6 +734,12 @@ Specifies the sub-string range a facet feature applies to. Start index is inclus
 
 ---
 
+### `org.hyperboards.authWrite`
+
+**Description:** Permission set granting create, update, and delete on every Hyperboards (org.hyperboards) record collection.
+
+---
+
 ### `org.hyperboards.board`
 
 **Description:** Configuration record for a hyperboard, wrapping an underlying activity or collection with visual presentation settings. Stored in the creator's PDS.

docs/design/permission-sets.md

@@ -197,6 +197,7 @@ Enumerates every `type: "record"` collection under `app.certified.*`:
             "app.certified.graph.follow",
             "app.certified.link.evm",
             "app.certified.location",
+            "app.certified.signature.proof",
           ],
           "action": ["create", "update", "delete"],
         },
@@ -321,15 +322,6 @@ The `AGENTS.md` "Adding / modifying a lexicon" checklist calls this out. Worth a
 check in the release process too (and ideally an automated test asserting each
 set lists exactly the `type: "record"` defs in its namespace).
 
-> **Known pending update.** PR
-> [#219](https://github.com/hypercerts-org/hypercerts-lexicon/pull/219)
-> (`feat/signature-support-v2`, HYPER-181) adds the `app.certified.signature.proof`
-> record lexicon, which does **not** exist on `main` yet and so is **not** in
-> `app.certified.authWrite` here. When #219 merges,
-> `app.certified.signature.proof` must be added to the set's `collection` list
-> (and re-published). The two PRs touch different files, so neither blocks the
-> other — this is just a follow-up to land after both.
-
 ## References
 
 - AT Protocol permission spec — permission sets:

lexicons/app/certified/authWrite.json

@@ -19,7 +19,8 @@
             "app.certified.badge.response",
             "app.certified.graph.follow",
             "app.certified.link.evm",
-            "app.certified.location"
+            "app.certified.location",
+            "app.certified.signature.proof"
           ],
           "action": ["create", "update", "delete"]
         }