raiffeisen-1.9.11.100 · ASSRAFIPI-135 / FKITDEV-9156

Per-release tracking hub for the Raiffeisen (PION / Myra) VUER OSS+CSS release 1.9.11.100. Two of its payload tickets (FKITDEV-8827, FKITDEV-8787) were merged into the release branch on 2026-08-10; the release itself is not tagged yet.

Release issue: ASSRAFIPI-135 (authoritative changelog) · internal FKITDEV-9156 Predecessor: raiffeisen-1.9.11.99 (the release branch was cut from that tag) Client name glue: YouTrack suffix RAFIPI → repo/customization name raiffeisen — see client-registry

State as of 2026-08-11 — merged to a BRANCH, not tagged, and not merged back

• Release branch chore/FKITDEV-9156-raiffeisen-release-1.9.11.100 exists in both vuer_oss and vuer_css.
• raiffeisen-1.9.11.100 is NOT a tag in either repo. Code is on the release branch only, so nothing is buildable/publishable by tag yet.
• Neither fix is on customization/raiffeisen nor on devel. Merge-back is still owed. Any new branch cut off customization/raiffeisen today silently loses both fixes.
• Both dev tickets are stale in YouTrack — nobody moved them after the merges (see YouTrack state is stale).

CORRECTION 2026-09-08 — the release IS tagged; the warning above is superseded on that point

Re-verified 2026-09-08 with git ls-remote + git ls-tree (not via rtk — see rtk-git-log-hides-merge-commits):

Fact	Value
Tag	raiffeisen-1.9.11.100, annotated, object eaeacd0799
Tagged at	2026-08-18 12:36 +0200
Commit	2352f5117f
Release branch	chore/FKITDEV-9156-raiffeisen-release-1.9.11.100 — at the same commit as the tag

Note the consequence for local work: the branch head recorded in Branch heads (verified 2026-08-11) (350d3e626b) is now 6 commits behind the tag, and those 6 commits touch files that face-comparison conclusions rest on. Read the tag, never the worktree — facekom-worktree-vs-tag-trap.

Release-state risk — RE-CONFIRMED 2026-09-08, and still open

customization/bin/raiffeisen-facecomparison-export.js exists only on this lineage (release branch + tag). Verified 2026-09-08 by git ls-remote + git ls-tree: it is absent from origin/customization/raiffeisen (fa983a0eba) and absent from devel.

A next cut from customization/raiffeisen therefore silently loses the export script, together with the SLARAFIPI-84 recovery work built on top of it (branch fix/SLARAFIPI-84-facecomparison-export-rejected, cut from this tag). The merge-back below is not housekeeping — it is what keeps a delivered partner feature from disappearing.

Branch heads (verified 2026-08-11)

Verified with gh + git ls-remote + an explicit-refspec fetch (+refs/heads/<branch>:refs/remotes/origin/<branch>) — mandatory in vuer_css, which has a narrowed fetch refspec that leaves origin/* stale on a bare git fetch origin <branch>; see narrowed-fetch-refspec-stale-devel-merge.

Repo	Branch	Head
vuer_css	chore/FKITDEV-9156-raiffeisen-release-1.9.11.100	95b3e73416a10b563b260c96bd5699b9b294bd76
vuer_oss	chore/FKITDEV-9156-raiffeisen-release-1.9.11.100	350d3e626b096456df722b8940871b41e3c74f92

Base tag for both: raiffeisen-1.9.11.99.

Changelog (from ASSRAFIPI-135)

Partner-side ticket ids, in the release issue’s own order — this is also the section order for the partner TjK (see tesztjegyzokonyv-partner-release-document-structure).

#	Partner ticket	Subject	Impl (FKITDEV)
1	ASSRAFIPI-124	CV document recognition v2 → v3	—
2	ASSRAFIPI-119	Arcösszehasonlítások eredményeinek kigyűjtése (face-comparison export)	FKITDEV-8827
3	ASSRAFIPI-18	—	—
4	CRRAFIPI-106	—	—
5	ASSRAFIPI-92	ImageId log	—
6	SLARAFIPI-59	girinfo feldolgozás issue	— (adjacent: FKITDEV-8581)
7	SLARAFIPI-60	”Already authorized” / “Already has some kind of room” (phantom room)	FKITDEV-8787
8	SLARAFIPI-62	logikai adategyezés dr issue javítása	—
9	CRRAFIPI-115	Liveness 2	—

For Agents

Only rows 2 and 7 have a verified FKITDEV implementation ticket + merged PR as of 2026-08-11. The other seven rows are changelog entries whose implementation was not traced in this session — do not assume they are unimplemented, and do not assume they are done either. Re-derive before cutting.

Merged payload (verified 2026-08-11)

ASSRAFIPI-119 ← FKITDEV-8827 — face-comparison export (vuer_oss)

Field	Value
PR	TechTeamer/vuer_oss#7971
State	MERGED 2026-08-10T06:36:09Z
Merge commit	297aa2fac1f69c15481e16acdc663edeb7414d75
Review	APPROVED by m3szi
Base	RETARGETED from release/FKITDEV-8902-raiffeisen-1.9.11.95 → chore/FKITDEV-9156-raiffeisen-release-1.9.11.100
Verification	its 3 files confirmed present on the .100 branch

Ships raiffeisen-facecomparison-export.js + FaceComparisonExportService. Design model: face-comparison-data-verdict-threshold-model (canonical) and face-comparison-different-face-db-query.

SLARAFIPI-60 ← FKITDEV-8787 — phantom-room self-heal (vuer_css)

Field	Value
PR	TechTeamer/vuer_css#3064
State	MERGED 2026-08-10T06:45:11Z
Superseded PRs	#3050 and #3051 — both CLOSED UNMERGED (both targeted customization/raiffeisen)
Verification	self-heal present on the .100 branch at server/socket/events/selfservice-v2.js:303-322; abort-path clear at :575

The delivery route changed: partner-branch PRs were abandoned in favour of a release-branch PR

The customization/raiffeisen-targeted attempts (#3050, #3051) were closed unmerged; the change actually shipped via a release-branch PR (#3064), and #7971 was likewise retargeted off the older .95 release branch. That is the reusable pattern here: for this partner, payload lands on the chore/FKITDEV-<n>-raiffeisen-release-<ver> branch, and customization/raiffeisen is updated afterwards (or not at all — which is the current gap).

Branch topology — where the two fixes actually live

graph TD
    TAG["tag raiffeisen-1.9.11.99"] --> REL["chore/FKITDEV-9156-<br/>raiffeisen-release-1.9.11.100<br/><i>oss 350d3e62 · css 95b3e734</i>"]
    PR7971["vuer_oss PR 7971<br/>FKITDEV-8827<br/><b>MERGED 08-10</b>"] --> REL
    PR3064["vuer_css PR 3064<br/>FKITDEV-8787<br/><b>MERGED 08-10</b>"] --> REL
    PR3051["vuer_css PR 3050 / 3051<br/><b>CLOSED unmerged</b>"] -.->|abandoned| CUST
    REL -.->|"NOT DONE — merge-back owed"| CUST["customization/raiffeisen"]
    REL -.->|"NOT DONE — no tag"| NOTAG["tag raiffeisen-1.9.11.100"]
    CUST -.->|"NOT DONE"| DEVEL["devel"]
    style TAG fill:#2d2d2d,stroke:#888,color:#fff
    style REL fill:#264653,stroke:#2a9d8f,color:#fff
    style PR7971 fill:#264653,stroke:#2a9d8f,color:#fff
    style PR3064 fill:#264653,stroke:#2a9d8f,color:#fff
    style PR3051 fill:#3d2020,stroke:#c44,color:#fff
    style CUST fill:#3d2020,stroke:#c44,color:#fff
    style DEVEL fill:#3d2020,stroke:#c44,color:#fff
    style NOTAG fill:#3d2020,stroke:#c44,color:#fff

YouTrack state is stale

Nobody moved the tickets after the 2026-08-10 merges

Ticket	Recorded state	Reality
FKITDEV-8827	State Pending, Blocker Review Needed	PR #7971 approved + merged 2026-08-10
FKITDEV-8787	State Pending, Blocker Review Needed	PR #3064 merged 2026-08-10
SLARAFIPI-60	Blocked / Blocker Release needed	code merged to the .100 release branch
ASSRAFIPI-119	Blocked / Blocker Release needed	code merged to the .100 release branch

Consequence for release scoping: the readiness union documented in the releases index and youtrack-ready-for-release-nusz-query keys off Blocker: {Release needed} / {Ready for release} — so these two will keep appearing as unshipped scope until someone transitions them.

Unanswered partner question — now answerable

Bence Varga, 2026-07-30 on SLARAFIPI-60: “melyik release-be tud ez belekerülni?” (“which release can this go into?”).

Never replied. The answer as of 2026-08-11 is 1.9.11.100 / ASSRAFIPI-135 — the fix is merged to that release branch. Worth sending, since the question is 12 days old and the questioner is the reviewer community for this flow surface.

Open items

• Tag raiffeisen-1.9.11.100 — DONE 2026-08-18 12:36 +0200, annotated tag eaeacd0799 → commit 2352f5117f (verified 2026-09-08)
• Merge back the release branch → customization/raiffeisen → devel, otherwise both fixes are lost on the next partner branch cut — still open, re-verified 2026-09-08: customization/bin/raiffeisen-facecomparison-export.js is absent from origin/customization/raiffeisen (fa983a0eba) and from devel
• Transition FKITDEV-8827 + FKITDEV-8787 out of Pending / Review Needed
• Clear Blocker: Release needed on SLARAFIPI-60 + ASSRAFIPI-119 once shipped
• Reply to Bence Varga on SLARAFIPI-60
• Confirm the delivery target (modern vuer-release project vs legacy vuer_build/partner/raiffeisen) — not verified in this session; see client-registry and vuer-release-cut-recipe
• Trace implementation for the seven un-traced changelog rows
• Finish the partner TjK (draft exists, has known defects — see below)

Partner test record (TjK)

A 2026-08-10 draft exists: Raiffeisen - Tesztelési jegyzőkönyv - VUER OSS CSS - Release 1.9.11.100.docx. Its structure was reverse-engineered into a reusable spec — tesztjegyzokonyv-partner-release-document-structure.

The two missing sections are already written: raiffeisen-1.9.11.100-tjk-sections holds the finished Hungarian ASSRAFIPI-119 and SLARAFIPI-60 sections with their evidence blocks, to be appended after the SLARAFIPI-62 section. It also lists what is still open — most importantly that the SLARAFIPI-60 fix covers the ALREADY_HAS_ROOM path only: Already authorized is deliberately not fixed, because the socket’s customerId / authorization is preserved by design, so a re-register/auth on the same socket can still throw it. The mobile A/B scenarios need a real Myra client and have not been run.

Known defects in that draft (fix before PDF export + attach):

• Body paragraphs mis-styled Heading2/Heading3 inside the SLARAFIPI-59 section → they pollute the TOC.
• Two empty Heading2 paragraphs before that section.
• SLARAFIPI-62 - Logikai adategyezés dr issue javítása — both subsections empty.
• issuu typo in the SLARAFIPI-59 heading (should be issue).
• The static Word TOC does not refresh on programmatic append — refresh in Word/Docs before export.

Attachment procedure (read-only recipe for finding/downloading prior ones): youtrack-tesztjegyzokonyv-attachment-recipe.

Local verification evidence (2026-08-11)

Both merged payloads were re-verified locally today, after the merges, on the release-branch code.

Suite	Result
vuer_css test/tests/unit/socket/events/selfservice-v2.test.js	76 / 76 pass — 12 of them the FKITDEV-8787 cases
vuer_oss RaiffeisenFaceComparisonExportService.test.js	23 / 23 pass
vuer_oss .dev-e2e/run-e2e.sh (8827 E2E harness)	green — produced a real dated CSV proving a different_face row exports with status=success

The E2E harness is untracked in the FKITDEV-8827 worktree: it spins a throwaway postgres:17-alpine on port :5544 via OrbStack. It is the only evidence path that exercises the export end-to-end against a real database rather than mocks, and it confirms the read-time-verdict model — different_face is a derived verdict, while the persisted row status stays success (see face-comparison-data-verdict-threshold-model).

Two environment gotchas hit while producing that evidence

• vuer_css worktree node_modules was out of sync with the branch lockfile — missing @babel/plugin-proposal-class-properties. Fix: yarn install --frozen-lockfile in the worktree. A worktree does not get its own install for free; switching a worktree onto a release branch can silently leave you on another branch’s dependency tree.
• rtk mangles git show <rev>:<path> argument handling, and swallows jest --verbose per-test lines. Use a python3 subprocess.run([...]) args list (no shell) for the git show, and jest --json --outputFile=<f> instead of --verbose to get per-test results. Same family as rtk-mangles-curl-and-pipes and rtk-git-log-hides-merge-commits.

Related

FKITDEV-8827 · FKITDEV-8787 · SLARAFIPI-84 · face-comparison-data-verdict-threshold-model · face-comparison-different-face-db-query · raiffeisen-1.9.11.100-tjk-sections · tesztjegyzokonyv-partner-release-document-structure · tesztjegyzokonyv-generation-flow · tesztjegyzokonyv-primer-prompt · youtrack-tesztjegyzokonyv-attachment-recipe · client-registry · release-process · vuer-release-cut-recipe · narrowed-fetch-refspec-stale-devel-merge · customization-branches · FKITDEV-8581 · FKITDEV-8788