General Bernardo Reyes to Ignacio Revueltas, Monterrey, 1 April 1886

TASK: take a partial decipherment further: General Bernardo Reyes to Ignacio Revueltas, Monterrey, 1 April 1886
This page: https://dbourdeau.github.io/cyphersolver/further/reyes1886.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/reyes1886.html (read it first: how the text was read, the key, the reading)
  Date:       1886
  Outcome:    key from adjacent plaintext · partial
  Read now:   41.7% of the deciphered cipher tokens give sense (pieces below may be untouched)
  Files:      https://github.com/dbourdeau/cyphersolver/tree/main/targets/reyes1886 (NOTES.md, key, transcription, reading, scripts)

OPEN GAPS (from NOTES.md, "## Remaining gaps")
  1. [open-codes: doable now] Groups 12, 20, 40, 53, 82 - blocker: open-codes; values from context only (ch, p, j, v, ch). 23 = n and 65 = ñ were first on this list; the integration check confirmed them on DLI.4.631.1 and DLI.3.416.1 (above). More "cifrada y traducción" letters of the channel (Dec 1885 - Apr 1886) in Fondo DLI would confirm the rest. The fondo's other cipher items found in the sweep list (Díaz letters) are in the President's key.
  2. [open-codes: doable now] "r{+a}nchero", the weakest word (raised by the reviewer) - blocker: open-codes; two departures, the writer's dropped a and 12 = ch from context. It fits the struck clear word and the "than a politician" contrast.
  3. [illegible: needs a new source] The struck clear word before R5 ("canalla"?) - blocker: illegible; struck through by the writer, nothing else decides it.
  4. [needs-physical-access: needs a new source] 524.1, right edge of page 1 - blocker: needs-physical-access; cut by the scan, a few groups there and the last line are lost (rows tagged in `transcription_524.txt`).

ALREADY TRIED (from NOTES.md, "## Escalation")
  [x] siblings: DLI.3.455.1, 3.524.1, 3.525.1, 4.623.1 and 4.630.1 opened; 524.1 gave the key; 455.1 p. 2 and 525.1 are in the President's four-digit code; 623.1 is the new table of 16 Mar 1886, which Reyes says he did not use.
  [x] clear-pages: the "Traducción" on 524.1 p. 2 used for the key and the held-out test; 634.1 has no decipherment.
  [x] known-keys: DLI.3.416.1 and DLI.4.631.1 (same key, with contemporary translations) opened at the integration check and decrypted with the frozen key: 91 right, 0 wrong; they confirm 23 = n and 65 = ñ.
  [x] print: four web searches in all (two by the contributor, two at the integration check, 12 Nov 2026: Reyes/Revueltas clave cifrada 1886 edition; Narváez on Mexican cryptography with Reyes, Garza Galán, Cervantes) and the catalogue's own check: only Narváez's 2019 SRE book and articles in general and Ríos Vázquez's thesis on Porfirian espionage turned up, none naming this letter. Narváez 2019 and the thesis were not opened; the Reyes papers' own printed edition, if any, was not found.
  [x] key-rebuild: the seven groups not in the frozen key filled from the clear text around the runs; 82 = ch holds at both of its places.
  [x] retry: every run decrypted again with the frozen key and the context values; `scripts/check_marks.py` passes.

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