Fiedmond to the Navy minister, Cayenne, 1779: the defence of Guiana in cipher

TASK: take a partial decipherment further: Fiedmond to the Navy minister, Cayenne, 1779: the defence of Guiana in cipher
This page: https://dbourdeau.github.io/cyphersolver/further/fiedmond1779.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/fiedmond1779.html (read it first: how the text was read, the key, the reading)
  Date:       1779
  Outcome:    key from adjacent plaintext · partial
  Read now:   70.0% of the deciphered cipher tokens give sense (pieces below may be untouched)
  Files:      https://github.com/dbourdeau/cyphersolver/tree/main/targets/fiedmond1779 (NOTES.md, key, transcription, reading, scripts)

OPEN GAPS (from NOTES.md, "## Remaining gaps")
  1. [open-codes: doable now] 75 unresolved words (24 in f9, 51 in f16): numbers absent from the key (552, 444, 403, 626, 778, 723, 430, 652, 441, 582, 192, 132, 219, 188, 256, 605, 695, 71, 189; in f16 576, 375, 289, 126, 112, 698, 765, 255, 155, 118, 245, 472, 274, 800, 740, 727 ...) and the river names 102, 515, 271, 720 - blocker: open-codes; most occur once or twice in the corpus and no table of this code is known
  2. [no-key-material: needs a new source] 636 probable words (159 in f9, 477 in f16; most rest on a "prob" value, usually a single aligned occurrence in the pairs, about 55% reliable) - blocker: no-key-material; the two pairs give too few occurrences, a further text of the time in this code would confirm or correct them
  3. [no-key-material: needs a new source] 309 restored words (values from context only, numbers read by the sense, values contradicted by the sense such as 398 = ils read "ap" and 461 = ef read "fe") - blocker: no-key-material; a third text of the time in this code (a decipherment of f9/f16, or the minister's answer in ANOM series B) would test them; not online
  4. [illegible: needs a new source] doubtful groups of the transcription (182/183 in 182.633 on views 010, 012, 023, 024; 801?/301, 605, 695, 71, 189) - blocker: illegible; overwritten or ambiguous figures, to be re-read blind on the images; 438 groups checked so far (views 009, 014, part of 022), the rest of f16 not checked at full resolution; the ANOM image route answered 403 on 12 Nov 2026
  5. [no-key-material: needs a new source] the two cipher/clear pairs of 1779 and 1780 and the earlier key K-Guy1780b.tsv are not in the repository, so the pair-derived values of the key cannot be verified here - blocker: no-key-material; held by the contributor, to be asked for (C14 51 ff. 98-111 and C14 52 ff. 15-19v transcriptions, K-Guy1780b.tsv)
  6. [no-key-material: needs a new source] 53 of the 59 context-only values of the key are untested by the held-out portion, which is now used up - blocker: no-key-material; no other untouched text in this code is known

ALREADY TRIED (from NOTES.md, "## Escalation")
  [x] siblings: C14 51 surveyed view by view (376 views) and C14 52 (338 views): cipher pieces f9, f16, f102 (+ clear copy) and the 1780 pair; no other cipher piece, no table
  [x] clear-pages: f102's clear copy (ff. 98-101) and the 1780 "Déchiffrement" (C14 52 ff. 17-19v) used as key material; the dispatch of 22 Mar 1779 and La Serre's papers checked as cribs (not parallel texts)
  [x] known-keys: Guiana 1757-62 (orvilliers1759), Bouillé's Martinique codes B (K1, K6, K8) and the minister's code M of 1777 tested: none applies
  [x] print: no edition found (catalogue vetting, our searches)
  [x] key-rebuild: K-Guy1780b from the two pairs, K-Guy1780c proposed by Claude Fable 5.2 and frozen, measured once
  [x] retry: every group re-decoded with the extended key K-Guy1780c and every word regraded (words_f09.tsv, words_f16.tsv); the blind re-reading of the doubtful groups on the images is not done yet, and the minister's answers in ANOM series B are not online

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