RFP-003 aggregate findings on v0.2.4 (2026-09-24)

Every issue, defect, coverage gap and open decision recorded in the four Logos QA documents below, in one register. Each entry keeps the source’s own severity and status and cites where it came from; nothing is re-graded here.

Candidate: Gateway v0.2.4, 98f492adff67bf62c22e04609f0810c196d6a0dc

Key	Source document	What it is
A	‣	Coverage grading of the twelve review-map test cases against the RFP hard requirements
B	‣	Requirements under the submitted milestones M1, M3 and M6 that still lack evidence, with proposed test-case variants
C	‣	Independent local run of the five release-runnable BTC cases in both directions
D	‣	Specification conformance hunt, findings /1 to /15, two independent passes plus merge adjudication

RFP baseline: logos-co/rfp@4e9b3c3d. Review map: Logos review map gist.

1. How to read this register

ID prefix gives the class: CODE code defect with a failing test, PKG packaging or deployment defect, APP released app defect, COV test coverage gap, DOC missing document or submission artifact, SPEC spec wording drift, DISP finding disputed between the two conformance passes, DEC decision Logos has to take.
Severity is copied from the source. D grades info, low, medium. B grades critical (blocks the milestone claim), gap (a clause is unproven), decision (a call for Logos). A and C do not grade; those rows show —.
Status is one of open, partly closed, closed, disputed, unconfirmed, decision pending.
Source cites the document key and the finding, row or section inside it.

2. Summary

Class	Count	Of which test-backed or confirmed by both passes
CODE code defects	4	4
PKG packaging and deployment	5	2
APP released app defects	6	—
COV test coverage gaps	17	—
DOC missing documents and artifacts	9	3
SPEC spec drift	2	1
DISP disputed	3	0
DEC decisions for Logos	4	—
Total	50

Highest-impact items, as the sources rank them:

CODE-4 the swap coordinator authorizes claims while a funding leg is absent or underconfirmed (F6, D/15, confirmed).
CODE-1 and CODE-2 the ZEC refund-deadline ordering that F4 requires is not enforced in code (D/1, D/2, confirmed).
CODE-3 one missing chain probe binary stops the whole maker (R3, D/3, confirmed).
COV-1 no case asserts that the cooperative BTC claim is a standard Taproot key-path spend (F2, B marks critical).
COV-3 no case cuts Delivery and Chat after the first lock (R2, B marks critical).
APP-4 the released Taker app has no ZEC flow, so ZEC-APP-001 is blocked (U6, B marks critical, D/14 confirmed).
COV-5 BTC-TIMING-001, the public-profile refund-ordering run, has never been executed (R6, S1).