scp81: RAM install over HTTP OTA (v2.1.8)

- shared _cap_apdu_sequence helper (INSTALL [for load] -> 240-byte LOAD
  blocks -> INSTALL [for install]); the SCP80 /api/ram-install path now uses
  it too (one source of truth; byte-level tests pin the APDUs)
- POST /api/scp81/ram-install: parses the .cap server-side and queues the
  APDU sequence as the SCP81 command script (one C-APDU per POST, runs on the
  card's next push); refused while a script is mid-run unless force
- /api/scp81/script reports the script kind (explore/none/custom/ram-install)
- tab: RAM install row (CAP file + SD AID + Queue button); RU strings
- docs: api.md, findings, AGENTS; service worker v145

docs/scp81-findings.md

@@ -202,8 +202,11 @@ Full session: 7/7 commands, all `X-Admin-Script-Status: ok`.
 1. **UI:** group the per-page R-APDUs under their logical command in the
    SCP81 tab (page merging/decoding for ELF and application listings);
    expose the framing options in the tab.
-2. **Load/store over SCP81:** RAM INSTALL/LOAD via command scripts using the
-   same recipe (one C-APDU per POST, pagination for long responses).
+2. **Load/store over SCP81:** implemented - `POST /api/scp81/ram-install`
+   takes a `.cap`, expands it with the shared `_cap_apdu_sequence` helper
+   (INSTALL [for load] -> 240-byte LOAD blocks -> INSTALL [for install]) and
+   queues it as the command script, one C-APDU per POST. Live install test
+   pending (needs a push with a suitable applet).
 
 ## Tooling