Diede and Reck, Hanoverian envoys at Regensburg, 1730: the type A letter cipher

TASK: take a partial decipherment further: Diede and Reck, Hanoverian envoys at Regensburg, 1730: the type A letter cipher
This page: https://dbourdeau.github.io/cyphersolver/further/diede1730.html

You are helping a public research project finish reading historical cipher letters. This one is read in part:
the key works, but some pieces are still open. Your job is to close one or more of the open gaps below.

THE READING
  Write-up:   https://dbourdeau.github.io/cyphersolver/diede1730.html (read it first: how the text was read, the key, the reading)
  Date:       1730
  Outcome:    key from adjacent plaintext · partial
  Read now:   3.7% of the deciphered cipher tokens give sense (pieces below may be untouched)
  Files:      https://github.com/dbourdeau/cyphersolver/tree/main/targets/diede1730 (NOTES.md, key, transcription, reading, scripts)

OPEN GAPS (from NOTES.md, "## Remaining gaps")
  1. [needs-physical-access: needs a new source] Nr. 1687 Relat. 17, 21, 25 (aufn 119-123, 142-144, 158-159; roughly 2,400 groups) not transcribed - blocker: needs-physical-access; the Arcinsys images were refused by the integrating session's network policy; the frozen key applies once they are transcribed
  2. [needs-physical-access: needs a new source] Nr. 1149/1 aufn 0006-0008 and 0102-0103 not transcribed; aufn 0004 groups 161-242 only raw exploration - blocker: needs-physical-access; groups 161-242 need a re-check of the transcription on the image; Arcinsys unreachable from the integrating session
  3. [needs-physical-access: needs a new source] transcribed runs of Nr. 1687 (aufn 004, 025-036, 056-057) decoded but not read word by word - blocker: needs-physical-access; doubtful digits and the partial glosses must be settled on the images; Arcinsys unreachable from the integrating session
  4. [open-codes: doable now] 17 doubtful key rows; word codes 281, 26, 279 (Nr. 1149/1 aufn 0003) and others - blocker: open-codes; too few occurrences in the transcribed material to fix them

ALREADY TRIED (from NOTES.md, "## Escalation")
  [x] siblings: all 605 images of Hann. 92 Nr. 1149/1 surveyed (contributor); type A in aufn 0003-0004, 0006-0008, 0102-0103. Hann. 92 Nr. 1146/2, 1146/3, 1149/2 and Hann. 9g Nr. 1424, 1491, 1673, 1676, 1691 not opened (Arcinsys unreachable from the integrating session); noted on the leads
  [x] clear-pages: the clear P.S. ad Relat. 16 (aufn 065R-068L) is the key's source; aufn 0003 gloss checked against the decode
  [x] known-keys: targets/mecklenburg1734 (WAINUT, #104) is a different system (a code); no other Hanoverian key of 1730 in the repository
  [x] print: no edition known; nothing on DECODE, Cryptiana or Lasry's lists (lead 1659 vetting, 2 Nov 2026)
  [x] key-rebuild: key rebuilt by EM alignment from the clear P.S. (166 rows), frozen and validated on aufn 0004
  [x] retry: the frozen key re-applied to all 3,630 transcribed groups of Nr. 1687 at integration (decryption-1687.txt); further reading needs the images

STEPS
0. Set up. If you can run a shell, fork and clone the repository and work inside it:
     git clone https://github.com/dbourdeau/cyphersolver.git
   Then read, in this order: CONTRIBUTING.md (how a contribution is sent and credited); README.md, sections
   "Repository layout" and "Conventions" (how readings are measured and named); targets/diede1730/NOTES.md in full, and the
   key, transcription and reading files it names; lang/README.md (shared language models).
   Work in targets/diede1730/. Add your findings to NOTES.md under a dated heading without rewriting what is there, and
   update the "## Remaining gaps" line of every gap you close. Keep WORKLOG.md there: one dated line per step
   (hypothesis, value tried, solver run, crib, control), failures included. Do not edit docs/ (the site is generated).
   If you cannot run a shell, fetch the files from the links above and keep your work in files you send with the issue.
1. Pick a gap. Start with the ones marked "doable now" (open-codes, not-attempted, left-open): the images and the key
   are online, so they need only work. A gap marked "needs a new source" (no-key-material, too-short, illegible,
   needs-physical-access) can be closed only by something new: a key
   or a deciphered sibling found elsewhere, a better image, a printed edition or calendar, a photograph from the archive.
   For those, search for that material first, and say where you looked even when you find nothing.
2. Start from the existing key and transcription in the folder. Do not rebuild the key from scratch, and do not
   re-read parts that are already read unless you find an error in them.
3. For a code group or sign value: list every place the group occurs, show how each reads with the value you propose,
   and say what still does not fit. For a passage: re-read it at the image and give the folio and line. For a missing
   letter or leaf: say where it is held and how it can be reached.
4. Measure again. Apply the key to the whole text, write the reading file, and count the share of cipher tokens that
   give sense (not an estimate). The reading is "complete" only when (1) at least 95% of its cipher tokens give sense;
   (2) no gap is left untried; (3) every letter in it is covered; (4) what stays open is scattered code groups or names,
   or pieces blocked from outside. Otherwise it stays "partial": say which gaps are still open and why.
5. Be honest. Mark every uncertain word with [?], leave unread groups as their numbers or signs, and never fill a gap
   with a plausible guess. A gap retried and still open, with what was ruled out, is worth reporting.

REPORT BACK
With a clone: open a pull request with your changes to targets/diede1730/. Say in the description which gaps you worked on,
  the share read before and after, and how you want to be credited (name, initials or handle, and a link).
Without one: open an issue: https://github.com/dbourdeau/cyphersolver/issues/new?template=further-reading.yml&title=Further+reading%3A+diede1730&page=diede1730.html
  Give the write-up, the gap you worked on (its line in Remaining gaps, or the code group, folio and line), what you
  propose, the evidence (every occurrence, the images or sources), the share read before and after, your step log,
  and the tools and AI model you used.
If you cannot open issues or pull requests, write this report for your human to send. Credit goes to the person who sends it.