Phase D — Benchmark formalisation + published latency + CI regression alert #99

Activity

1. hyperpolymath

   added

   majorMajor / load-bearing workMajor / load-bearing work

   requirements-targetTracked requirements-target item (joint-close)Tracked requirements-target item (joint-close)

   on May 17, 2026
2. hyperpolymath

   added a parent issue on May 17, 2026

   • http-capability-gateway tier-2 production-wiring (ADR-0004) #91
3. hyperpolymath

   added 5 commits that reference this issue on May 20, 2026

   feat(perf): Phase D benchmark harness scaffold (standards#99 / #91 ch…

   ...

   385ccf7

   perf(d-2): wire in-process loopback backend so proxy-200 scenario mea…

   ...

   2798aed

   perf(d-2): wire in-process loopback backend so proxy-200 scenario mea…

   ...

   da84d75

   perf(d-3): dedicated trust-header rewrite + mTLS handshake scenarios …

   ...

   c82be8d

   perf(d-4 bootstrap): workflow_dispatch automation for baseline collec…

   ...

   d01c086
4. hyperpolymath

   added

   cicdCI/CD: workflows, actions, lockfiles, pins, runners, release gatesCI/CD: workflows, actions, lockfiles, pins, runners, release gates

   on May 30, 2026
5. hyperpolymath commented on May 30, 2026

   

   hyperpolymath

   on May 30, 2026

   OwnerAuthor

   More actions

   cicd triage 2026-05-30: Phase D remains blocked on Phases A→C (per #91 ADR-0004 phase ordering). Phase A (#96) is open, Phases B/C are sequentially gated. Leaving open with cicd label as the benchmark-CI work is the right ultimate scope. Will become actionable when Phase C lands.
6. hyperpolymath

   closed this as completedin boj-server#168on Jun 1, 2026
7. hyperpolymath

   added a commit that references this issue on Jun 2, 2026

   perf(d-3 followup): harden compare.exs against schema drift (standard…

   ...

   4cda8d7