Frozen document. Dates and status refer to its original source. Private resources and unreviewed images are unavailable.
BFF schema and transport amendment review
Date: September 30, 2026. Scope: the accepted Fastify/TypeBox/private-gRPC architecture amendment, ADRs 0011 and 0012, related diagrams, worker instructions and Journey Docs links. This was a bounded document-consistency review, not a runtime security audit or the two-axis code-review skill.
The review worker used GPT-6.1 Sol with medium reasoning. The main agent checked current package/adapter code, primary documentation and the owner's explicit scope confirmations. Token and turn runtime come from the transcript pipeline; no separately measured review duration or token allocation is asserted here.
| Finding | Severity | Mitigation | State |
| The system-context legend said solid paths were implemented while the new TypeBox path was marked planned. | P3 | Reworded the legend to separate delivered case/evidence paths from planned TypeBox/gRPC migrations. Updated stale private-evidence progress wording. | Verified resolved by the same review worker. |
| Greptile finding 4142681608 on PR 69: the Docs viewer test still required exactly 22 links after this amendment added four destinations. | P1 | Replaced the fixed count with a required-destination subset covering the existing guarded links and all four additions. Every destination must be unique, use the safe viewer and resolve to a document. Existing traversal and rendering-escape checks remain. | Focused regression reproduced and passed after the fix. |
The reviewer reported no other actionable findings, and its focused recheck reported no further findings. CMS ownership, browser sessions, durable delivery and HTTP compatibility remain preserved in the recorded design.
The Greptile regression was checked with rtk proxy env PYTHONDONTWRITEBYTECODE=1 python3 scripts/record_sdlc_command.py --phase unit --output [private location omitted] -- python3 -m unittest tests.test_capture_journey_metrics.JourneyPhaseMetricsTests.test_docs_tab_uses_safe_html_viewer_for_every_document -v. Before the test change, it failed with 26 != 22; afterward, the one focused test passed. Both runs recorded their actual exit status and elapsed time in the primary checkout's ignored command-metrics log. A successful Greptile check alone does not establish that a reported finding is fixed.
Validation: 50 added local links resolve; the two ADRs and design render through the existing Journey document viewer, retaining the Mermaid block; Git whitespace checking passes. This does not claim browser Mermaid rendering, installed TypeBox packages, a working gRPC channel or qualified payment workflows. Those require the implementation gates.