Lebel to Charles Emmanuel I of Savoy, 1593

TASK: take a partial decipherment further: Lebel to Charles Emmanuel I of Savoy, 1593
This page: https://dbourdeau.github.io/cyphersolver/further/lebel1593.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/lebel1593.html (read it first: how the text was read, the key, the reading)
  Date:       1593
  Outcome:    known key applied · partial
  Read now:   98.0% of the deciphered cipher tokens give sense (pieces below may be untouched)
  Files:      https://github.com/dbourdeau/cyphersolver/tree/main/targets/lebel1593 (NOTES.md, key, transcription, reading, scripts)

OPEN GAPS (from NOTES.md, "## Remaining gaps")
  1. [illegible: needs a new source] no. 62 f. 130v: ~6 signs under the recto's ink before code 46, and one blot (= 1 sign, probably i) - blocker: illegible; bleed-through and blot, dense on both sides.
  2. [no-key-material: needs a new source] no. 62 f. 130v codes 223 and 247, and the 8-sign run on line 1 (a e n l/s t s o o m a) that does not segment - blocker: no-key-material; no gloss, single context under bleed.
  3. [illegible: needs a new source] no. 62 recto, 10 letter signs (4 after the clear "que" at the head, 1-2 in l. 8, a stray "11" in l. 3) - blocker: illegible.
  4. [illegible: needs a new source] no. 11, ~6 letter signs in four short spans (l. 4 a(i)lles, l. 6 second? under a smudge, l. 20 au(?), v10 entre(m)ettant) - blocker: illegible.
  5. [no-key-material: needs a new source] M-grade code values: no. 11 305, 130, 292, 106, 50; no. 62 275, 69, 292, 109, 137, 278, 240, 100, 253, 30, ⅅX; no. 100 22, 27, 49, 50, 104, 150, 153, 154, 161, 230, 235, 241, 258, 260, 274, 278, 302, 305, XC - blocker: no-key-material; no surviving gloss (every decipherment in this key harvested), only the office nomenclator would confirm.

ALREADY TRIED (from NOTES.md, "## Escalation")
  [x] siblings: fr. 3983 no. 80 (and its decipherment f. 167), fr. 3984 f. 182, fr. 3985 f. 23 opened and harvested (section 4b). Still to open: BnF esp. 336 nos. 79-81, same key.
  [x] clear-pages: f. 167 (no. 80's decipherment sheet) checked; no clear copy of nos. 11, 62, 100 found in fr. 3983-3985 near the letters.
  [x] known-keys: Tomokiyo's savoy.htm key (the key of this series); his commented-out league.htm guesses for ~90 codes of f. 130 compared.
  [x] print: Tomokiyo (savoy.htm, league.htm) read; no printed reading of these letters found as far as checked.
  [x] key-rebuild: letter-sign corrections (section 5) and code values by alignment with the contemporary decipherments and by context.
  [x] retry: second sign-by-sign pass on all three letters with the corrected key and the harvested codes; codes regraded H/C/M/I.
  [x] second: harvest (21 Sept): fr. 3984 f. 182r-v re-read at higher resolution, ~40 more values (85 Monsieur, 64 le, 113 celuy, 114 eulx, 331 disoit, 349 estoit, 400 promettre ...; 257 glossed "en la faveur de" once, so ambiguous; the old "115 celuy" was 113). BnF esp. 336 (ark btv1b100325613): nos. 79 (canvases 268-269), 80 (272-273), 81 (270-271); only no. 81 is glossed (368 ma, 408 part, 359 ils, 383 ne). fr. 3985 f. 23v/24 blank/address.
  [x] image-processing: f. 130v bleed-through removed by registering the mirrored recto (patch-wise warp, ~1 px) and whitening bleed-level pixels.

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