Two things flagged while adding the `updated` finding. DESCRIPTION. The loader indexes on it, and it listed only the M0→M3 surface — so a search for reproject, OTA, media, or the Update trap would not route here, which is precisely when someone needs it most. Now names the control surface, reproject, and the Mastodon `updated` trap, with an explicit "read before touching AP delivery, edits, media, or deploying". DEPLOY SECTION. It predated 0.0.2 and read as though deploys were still a manual stop/install/start. Now records that they are OTA, verified twice hands-off — and the one-off exception worth knowing: the 0.0.1→0.0.2 hop itself needed a manual restart because the OLD code had no handler for the sidecar to push to. Any app gaining a control surface for the first time has the same one-off. Also folded in three deploy facts learned today that were nowhere: - the vendor list is DERIVED from package.json's file: deps, with the ~10-day silent-failure story that motivated it - the declare-deps guard checks the DECLARATION, not disk presence, since a hoisted transitive dep passes the latter — the very bug it exists to catch (bare-os was waved through). Dynamic import() is still invisible. - ⚠ a UDS path is capped near 107 bytes; a long AP_SOCK fails to bind with "invalid argument" and the control surface degrades SILENTLY while HTTP keeps serving. Cost me a false negative during the 0.0.2 smoke test. Stale test count corrected 70/254 -> 81/275. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>