Ormond to his son Arran, 24 January 1677/8: twenty figures set as a trial

TASK: take a partial decipherment further: Ormond to his son Arran, 24 January 1677/8: twenty figures set as a trial
This page: https://dbourdeau.github.io/cyphersolver/further/ormond1678.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/ormond1678.html (read it first: how the text was read, the key, the reading)
  Date:       24 January 1677/8
  Outcome:    external key matched · partial
  Read now:   50.0% of the deciphered cipher tokens give sense (pieces below may be untouched)
  Files:      https://github.com/dbourdeau/cyphersolver/tree/main/targets/ormond1678 (NOTES.md, key, transcription, reading, scripts)

OPEN GAPS (from NOTES.md, "## Remaining gaps")
  1. [no-key-material: needs a new source] figures 445, 342, 726, 700, 720 (1680 numbers 438, 335, 719, 693, 713) - blocker: no-key-material; no gloss for these numbers anywhere in HMC n.s. v, none in Tomokiyo's table. Alphabetical bracketing gives only the section: 438 after lo 435 (l-), 335 before h 336 (g-/h-), 693, 713 and 719 among the s- entries.
  2. [no-key-material: needs a new source] figures 58, 54, 32, 440 (1680 numbers 51 e, 47 a, 25 c, 433 le) and 425 (418 King) - blocker: no-key-material; values from the key's regular order and from context only; no gloss in print for these numbers.
  3. [too-short: needs a new source] whether +7 holds over the rest of the table - blocker: too-short; 20 figures, no repeats, and no other passage in the 1678 numbering in HMC n.s. iv-v.
  4. [needs-physical-access: needs a new source] an interlinear or marginal gloss on the sent letter or on Ormond's retained copy - blocker: needs-physical-access; NLI MSS 2335-2362 (Ormonde papers 1665-80), letter of 24 Jan 1677/8 in the bundle catalogued as MS UR 006261; not digitised. Arran's papers (Bodleian Carte MSS; MS. Carte 50 fols 439-440 reported by cipher-lab as a January 1678 Ormond-Arran cipher, not seen) may hold the letter as received, perhaps deciphered.

ALREADY TRIED (from NOTES.md, "## Escalation")
  [x] siblings: every Ormond-Arran letter of Jan-Feb 1678 in HMC n.s. iv read (pp. 92-107); Arran's replies do not repeat or answer the figures. The IA text of vols. iv-v scanned for other figure runs: none in the 1678 numbering.
  [x] clear-pages: the clear text of the same letter gives the subject (Douglas, Mansell, Granard) and fits the reading ("but it seems to Ormond not credible"); no further crib.
  [x] known-keys: the 1678 two-letter code is ruled out (not numeric); Longford 1 (1680) fits with +7 (13 Nov 2026); Longford 2 and 3 tested by the contributor over offsets -150..+150: no fit (max 12/20 and 4/20, no word).
  [x] print: HMC n.s. iv-v (all Longford 1 glosses, pp. 454-498), cryptiana charlesii2.htm. HMC 6th Rept. App. not seen.
  [x] key-rebuild: alphabetical bracketing of the five open numbers gives only their initial sections (Remaining gaps); no value can be fixed from 20 figures.
  [x] retry: every figure re-run with the shifted key and Tomokiyo's table as published (14/20) and with the contributor's values (15/20); strict 10/20 attested.

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/ormond1678/NOTES.md in full, and the
   key, transcription and reading files it names; lang/README.md (shared language models).
   Work in targets/ormond1678/. 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/ormond1678/. 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+ormond1678&page=ormond1678.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.