v1.46.02026-11-15
- Qualify Soviet POW enquiries by archival remit, add source routes for clergy families and digitised Kharkiv records, and distinguish Yandex participant-index coverage from the underlying record (#269, #273, #277, #278).
- Compare baptism and birth dates using the event and calendar in each source. Check the scope and age coverage of confession lists, the identity and binding order of parish records, and alternate readings of names and narrow date ranges (#270, #271, #272, #274, #275, #281).
- Qualify archive and viewer access observations, record the actual login state before reporting image access, and carry forward user-supplied readings with their provenance (#276, #279).
- Check shareable evidence fields and attachments for indirect identification, including names of informants outside the tree and identifying source titles (#280).
v1.45.02026-11-14
- Recover UTF-8 characters split at eligible GEDCOM 5.5.1 continuation boundaries during local validation, with a warning and without changing the source file (#263).
- Add an offline GWAR surname comparison for saved results with provenance and coverage retained (#266).
- Add qualified Lithuanian archive, volunteer index and surname-dictionary routes, and distinguish catalogue coverage from actual document access (#267).
- Check task-owned browser tabs before finishing or stopping, and report what was actually read, what is new, and why a significant repeat is needed when resuming a search (#264, #265).
v1.44.02026-11-13
- Improve the evidence audit’s reporting for composite artifact group labels, missing search-log links and out-of-scale confidence. Keep supported single-source claims conservative when the reason is recorded (#244, #255).
- Restore isolated-script and module invocation for the GEDCOM checker. Flag unusual years in 5.5.1 exact header and change dates for manual review (#254, #257).
- Check doubtful letters against competing forms, examine relevant parish-register parts and copies, use annual death summaries to prioritize reading, and qualify dated family mentions and only-candidate claims (#249, #250, #251, #252, #253).
- Describe archive viewer and search limits, distinguish FamilySearch catalogue and index coverage, and keep signed-in DNA work within the provider’s permitted methods (#247, #256, #258, #259).
- Qualify negative archival replies, add Krasnoyarsk reference routes, and verify surname stories and executor handoffs in the existing workflow (#248, #260, #261).
- Add historical guidance on local newspaper notices for court divorces and on interpreting marriage wording, dates and titles in transitional parish registers (#245, #246).
v1.43.02026-11-12
- Check Basharchive frame matches and qualify Genotek's archive and locality filters. Check FamilySearch's image-browse tree and paging alongside its catalogue before drawing coverage conclusions (#235, #236).
- Keep written family questionnaires neutral. Use relevant headings, parallel copies and the wording of household relationships to read confession lists, preserving contradictions and unverified links (#237, #238).
- Separate loss reports, demobilisation destinations and later evidence. Check the effects of military search filters and distinguish unavailable images from missing records. Resolve field-post and unit-name changes with dated documents, and keep party-card chronologies tied to dated records (#239, #240, #241).
- Preserve the sources, locators, supported identities and meaningful qualifications of claims retained during biography edits (#242).
v1.42.02026-11-11
- Use godparents and marriage sureties as dated leads, check composite parish volumes before concluding that years are missing, and review relevant changes before handing off a new shareable version (#210, #211, #212).
- Check browser targets and access barriers before continuing queued actions, and verify that a downloaded PDF covers the relevant pages before counting them as reviewed (#214, #216, #218).
- Expand qualified occupation-record and regional catalogue routes for Rostov, Kursk, Tomsk and Grodno. Read relevant finding aids and distinguish catalogue, film and image coverage. Use FamilySearch download controls within the applicable copy permissions (#223, #225, #226, #227, #232).
- Match archive correspondence to the receiving institution, check practical payment terms, coordinate sends and shared register IDs, and track substantive community replies in the existing case plan (#228, #229, #230, #231).
- Verify strong military matches in the full card, compare record groups and burial lists, and distinguish dates and source claims in loss records. Separate archival routes for imprisonment and special settlement, and qualify searches filtered by recent catalogue updates (#219, #220, #221, #233).
v1.41.02026-11-10
- Reduce false GEDCOM lint warnings for ordinary birth-family links, recognized spouse labels and exact header/change dates. Keep disputed or ambiguous parent roles and unsupported date contexts explicit (#201).
- Check infant deaths before treating a namesake as an adult candidate, distinguish name-day recollection from birth evidence, and preserve unresolved Roman-numeral month readings without inventing a precise date (#202, #203, #205).
- Read FamilySearch change history against current state before planning a correction, keeping uncertain people separate and changes within existing authorization (#206).
- Add qualified Ukrainian registration, voter-list and court routes and Russian civil-registration, repression-file and burial routes. Distinguish catalogue or public-copy coverage from actual access, preserve record provenance, and check current rules with the holder (#204, #207).
- Add five qualified catalogue, biography and historical-place leads. Generalize useful observations on composite books, duplicate copies, archive cards, source tabs and military context without carrying case-specific details or alternate access recipes into the catalogue (#208).
Validation: 119 unit tests passed without skips; eval YAML parsed with 177 unique scenario IDs. Local links, version metadata and diff checks passed. ClamAV scanned the exact 92-file tree with no threats detected.
v1.40.02026-11-09
- Add an optional local UTF-8 GEDCOM lint helper with bounded version-specific structural checks and selected case-register comparisons. Correct relationship matching and diagnostics, preserve valid version-specific forms, and make unsupported schema, calendar, pedigree, citation and importer checks explicit (#199).
- Add generalized Ukrainian archive routes for Archium, Poltava, Sumy, occupation-administration lists and Hetmanate revisions. Replace case-specific fingerprints and bulk-retrieval recipes with scoped search, accurate provenance and qualified coverage; a year filter does not establish living status (#196).
- Refine targeted checks of short household kinship formulas and their referents, without treating every kinship term as parenthood or requiring a crop for every readable record (#197).
- Add BillionGraves as a qualified community cemetery lead and consolidate source selection in the existing workflow. Respect its source-specific automated-access restriction, distinguish photographs from transcriptions and GPS coverage, and treat the FamilySearch collection as a dependent route rather than corroboration (#198).
Validation: 116 unit tests passed without skips; all eval YAML parsed with 168 unique scenario IDs; version/date and local-link checks passed. Local ClamAV scan of all 91 tracked files: no threats detected.
v1.39.02026-11-09
- Refine unindexed FamilySearch navigation with qualified DGS/item routing, film-title checks and mirror spellings. Distinguish public metadata from authenticated search and reuse existing access and coverage guidance (#184).
- Add a privacy-scoped route to published citizenship decrees and extend GASO finding-aid navigation. Distinguish a decree's statements from independently established family relationships, and clerical personnel records from parishioner lists (#185, #186).
- Consolidate authorized result handoffs, unresolved application decisions and matching delivery provenance in the existing coordination workflow. Preserve explicit user budgets across continuations without introducing a queue, framework or default quota (#187, #188).
- Keep plans conditional when living status is unknown, calculate kinship from actual relationship paths, and distinguish chat/export timestamps from photo capture dates. Correct the proposed cousin-degree example and avoid inferring timestamp semantics from a filename (#189, #192, #193).
- Extend qualified Chuvash, Volga German, Novgorod, Don, Tambov, railway and Kazakhstan catalogue routes. Preserve community-source labels, contributor observations and actual access limits (#190, #191, #194).
Validation: 87 unit tests passed without skips; eval YAML parsed with 167 unique scenario IDs, version/date and local-link checks passed. Local ClamAV scan of all 89 tracked files: no threats detected.
v1.38.02026-11-07
- Verify that archive viewers show the selected frame or index cards before counting them as reviewed. Consolidate loading and retry guidance, preserve index-only scope, and qualify gaps in interleaved parish-book sections (#174, #182).
- Add the Ingria Archive as an optional transcription and record-image lead, with publisher-reported coverage, reconstruction limits and task-scoped access (#175).
- Add a focused Armenia and South Caucasus research route and qualified Samara census, Shushi inscription and RKKA unit-reference leads. Keep source observations attributed, distinguish records from derived indexes, and quarantine the Shushi publication's exclusionary political narrative (#176, #177).
- Correct SQLite Unicode matching guidance and preserve language-aware spelling variants. Add original, optional family-interview prompts through the existing testimony and privacy workflow; replace the proposed copied course handout (#178, #179).
- Add the RVIO memorial-site map as a class C lead, separating user-submitted descriptions from individually checked inscription images and qualifying untested coverage (#181).
Validation: 87 tests passed without skips; eval YAML, version/date and local-link checks passed. Local ClamAV scan of all 89 tracked files: no threats detected.
v1.37.02026-11-06
- Add a qualified Bashkir revision-list index and refine Ufagen search and settlement-name disambiguation. Preserve transcription provenance, bounded coverage and date-specific locality checks (#167, #170).
- Add Chișinău notarial inventory and Arcanum newspaper routes, with separate checks for catalogue descriptions, OCR, original documents and access (#168).
- Improve metric-book month identification and handling of OCR or model disagreement. Preserve unresolved readings and distinguish birth from baptism (#171).
- Record dated Ukrainian archive restrictions affecting Belarusian applicants with current applicability qualified. Add Belarus civilian-camp, auction and optional public web-archive routes with provenance and access boundaries (#172).
All 87 unit tests passed. Diff, YAML and version checks passed. ClamAV 1.5.4 scanned all 87 tracked files with daily 28175 and detected no threats.