The “nueva clave”: three Maderista telegrams of April 1911

TASK: take a partial decipherment further: The “nueva clave”: three Maderista telegrams of April 1911
This page: https://dbourdeau.github.io/cyphersolver/further/nuevaclave1911.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/nuevaclave1911.html (read it first: how the text was read, the key, the reading)
  Date:       1911
  Outcome:    ciphertext-only break · partial
  Read now:   80.0% of the deciphered cipher tokens give sense (pieces below may be untouched)
  Files:      https://github.com/dbourdeau/cyphersolver/tree/main/targets/nuevaclave1911 (NOTES.md, key, transcription, reading, scripts)

OPEN GAPS (from NOTES.md, "## Remaining gaps")
  1. [no-key-material: needs a new source] A validation of the turning grille: the only held-out telegram is spent; another telegram in the grille, not yet seen, would be needed - blocker: no-key-material; none is known among the 136 coded pieces of the fonds harvested so far
  2. [needs-physical-access: needs a new source] 1561.5-13: letters 29, 38, 57, 68, 87 and the extra letter near 73 to be checked on the original; the two single "S" - blocker: needs-physical-access
  3. [too-short: needs a new source] The pencil letters "v e" above ESSFP on 1551.3-4 - blocker: too-short; two letters, not explained by the grille
  4. [needs-physical-access: needs a new source] The held-out telegram 1561.3-13: its cipher is not in the repository, only its hash, so a third party cannot repeat the failed measure (its first block, 64 letters never sent to the model, read as Spanish) - blocker: needs-physical-access
  5. [needs-physical-access: needs a new source] A second reader's check of the transcriptions against the CEHM images - blocker: needs-physical-access; the images may not be redistributed, and visor.cehm.org.mx failed TLS verification in the integrating session

ALREADY TRIED (from NOTES.md, "## Escalation")
  [x] siblings: the eight telegrams of the Clave G.A. test and 1561.7-13 (Clave G.A., `../mccarty1911/`) opened; none is in the grille
  [x] clear-pages: none of the three is in the typed decipherments CMXV.18.1795.1 and none carries a gloss
  [x] known-keys: every card of the fonds (CMXV.16.1557.1) tried on the five telegrams, group by group: none reads them (best coverage 0.50 < 0.70)
  [x] print: no printed edition of these telegrams is known; Narváez 2011 and 2019 not available to the project
  [x] key-rebuild: columnar transposition (widths 2-15) and Caesar shifts failed; the grille was proposed by an AI model from the ciphertext
  [x] retry: the shifted blocks were retried with the declared repairs (one deletion, one insertion)

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