Christian V to his envoys in Stockholm, 25 May 1673: the closing cipher block

TASK: take a partial decipherment further: Christian V to his envoys in Stockholm, 25 May 1673: the closing cipher block
This page: https://dbourdeau.github.io/cyphersolver/further/christianv1673.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/christianv1673.html (read it first: how the text was read, the key, the reading)
  Date:       1673
  Outcome:    key from adjacent plaintext · partial
  Read now:   70.6% of the deciphered cipher tokens give sense (pieces below may be untouched)
  Files:      https://github.com/dbourdeau/cyphersolver/tree/main/targets/christianv1673 (NOTES.md, key, transcription, reading, scripts)

OPEN GAPS (from NOTES.md, "## Remaining gaps")
  1. [open-codes: doable now] five of the six unresolved words and the two restored ones of the closing block (groups 32, 320, 348, 384 twice, 646, 906) - blocker: open-codes; the letter reads but these code groups do not: none is glossed in images 32-43, and the syllable blocks give only the initial of 384 (a-) and 646 (k-); another order in the same code would fill them
  2. [illegible: needs a new source] la·g·ge·n·s (T05): every group has a value but the word does not construe - blocker: illegible; a misread sign in our transcription is the likely cause ("Flaggens" would need an f), to be checked on the original image
  3. [needs-physical-access: needs a new source] the verso of the loose decipherment leaf (image 9) - blocker: needs-physical-access; it was not filmed and might carry the decipherment of the closing block; only Rigsarkivet can say
  4. [illegible: needs a new source] the overwritten group in T04 (image 11 line 1), 841 or 541 - blocker: illegible; the last digit is blotted and the first is drawn like this hand's 5 as much as its 8; the full-size online image does not decide between "Indulgencien, tid" and "indulgence for en tid"
  5. [illegible: needs a new source] a blind re-reading of the other doubtful signs of the closing block (T02 Q, T07 768 lam) - blocker: illegible; seen at the resolution served online, not yet re-read blind
  6. [no-key-material: needs a new source] the twelve probable words (Indulgencien, udstirkelse, saaledes, Sammentegn, aldre, Kronede, strygen in T12, upaakieret, huis, Fundament, Exempel) - blocker: no-key-material; each rests on a value inferred from the syllable blocks, on a single gloss or leaf attestation, or on a doubtful sign, and the unit holds no other text in the 1673 hand to confirm them
  7. [needs-physical-access: needs a new source] prior art outside the repository (an edition of the order, Rigsarkivet's inventories) - blocker: needs-physical-access; the printed volumes named under Prior art were opened in Daniel Bourdeau's vetting passes, not by the contributor or at the integration check, and the inventories are not online

ALREADY TRIED (from NOTES.md, "## Escalation")
  [x] siblings: all 62 images of unit 261588 checked on contact sheets; cipher only on images 8-11 (1673) and 32-43 (1674); the three glossed orders of 1674 transcribed with their glosses and used for the key and the held-out test
  [x] clear-pages: the loose leaf at image 9 right is the chancery decipherment of the first block only (aligned group by group); no other clear copy of the order in the unit
  [x] known-keys: the only key material known for this code is in the unit itself (1674 glosses and the 1673 leaf); DECODE, Tomokiyo and Lasry have nothing (Daniel's vetting); no printed key found
  [x] print: Danmark-Norges Traktater 6, Vaupell, Jørgensen, Fryxell and Danske Samlinger (Daniel's two passes, 11 Nov 2026): the order is not printed; our web search found no edition
  [x] key-rebuild: key extended by the alphabetical syllable blocks (486 du, 534 fu inferred; 590 huis from the h block and a gloss); 384 and 646 bracketed to an initial; nothing else can be inferred for 32, 320, 348, 906
  [x] retry: every unread group searched in all glosses of images 32-43 (42-43 after the measurement) and in the leaf; the reading regraded with key v2 and the sign table (working fiches 84.6% with key v1, then 86.2% with key v2 on a list short of three certain words; recount 86.8%; all three by the contributor's count of certain + probable words, which the integration check replaced by 70.6%, certain words only)

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