Johan Banér to Torsten Stålhandske, Hof, 29 December 1640

TASK: take a partial decipherment further: Johan Banér to Torsten Stålhandske, Hof, 29 December 1640
This page: https://dbourdeau.github.io/cyphersolver/further/baner1640.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/baner1640.html (read it first: how the text was read, the key, the reading)
  Date:       1640
  Outcome:    key from adjacent plaintext · partial
  Read now:   89.8% of the deciphered cipher tokens give sense (pieces below may be untouched)
  Files:      https://github.com/dbourdeau/cyphersolver/tree/main/targets/baner1640 (NOTES.md, key, transcription, reading, scripts)

OPEN GAPS (from NOTES.md, "## Remaining gaps")
  1. [needs-physical-access: needs a new source] S2 name after "Johann" (11 tokens, read "ohrspacbuet", plus the lone n after [513]) - blocker: needs-physical-access; the figures are confirmed on the manuscript and every value is fixed by other words (12 = p since 5 Oct), so the only known copy is corrupt; the sent original or a register copy in Banér's papers (Riksarkivet) is needed and is not digitised.
  2. [needs-physical-access: needs a new source] S5 "eisen o vi rechte" (14 tokens), "o ?" before "ein guten" (2), the stray e in "sobaldt e ich" (1) - blocker: needs-physical-access; figures confirmed on the manuscript, values fixed elsewhere, so the copy is corrupt; only another witness would settle them.
  3. [no-key-material: needs a new source] Code words 361, 442, 464, 508, 513, 568, 767, 773, 775 (766, 770, 772, 778, 783 read as letters) - blocker: no-key-material; no key survives (none of the Banér keys on DECODE is this one), each occurs once, and context gives only the sense.

ALREADY TRIED (from NOTES.md, "## Escalation")
  [x] siblings: DECODE has no record of this letter; the Riksarkivet key box II (R4103-R4329, 100+ records) scanned by API and cover labels; Banér keys R4122, R4123, R4325 and R4266 opened and transcribed.
  [x] clear-pages: the letter's clear text used throughout as context (every crib comes from it); no decipherment on the pages posted.
  [x] known-keys: R4122 (Horn-Banér), R4123 and R4325 (Banér 1634), R4325's third and fourth alphabets, R4266 tried as is and at offsets -30..+30: no fit.
  [x] print: web search for the letter, Cipherbrain comments, EMLO, Oxenstierna's printed letters (only Banér to Oxenstierna): no reading.
  [x] key-rebuild: key rebuilt from cribs by multiset annealing and word-by-word extension (above).
  [x] retry: (5 Oct 2026): unread stretches re-transcribed at 2x from the scan; S6 12 restored (12 = p); S5 candidate readings scored in context, none fits; sense measure written (`measure_sense.py`).
  [x] retry: manuscript scans fetched (Museo Galileo) and every line re-read; four figures corrected; every unread stretch re-run with the full key and with digit-confusion emendation (`emend.py`); S1 read (Jobs[t]), S7 completed.

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