{
  "body": "Perri reports standalone spt-core 0.69.0 on HFENDULEAM: unpiped endpoint list --show-all takes 3822, 10120, 10105ms, each rc=0 and byte-identical complete 2497-byte output. Three adapter field traces also show long roster stages. No adapter-imposed subprocess timeout; bare CLI reproduces. Unreachable peers are correlated, not established cause.\n\nIdentify the waiting stage and remove the diagnosed unnecessary delay while preserving full roster, suspended rows, local merge and truthful unavailable state. Do not substitute an empty/partial roster, move reads past destructive consumption, or widen a harness-specific timeout. Distinguish network deadline, local contention and metadata cost before choosing a fix. Public docs promise bounded identity-only whoami, not a numerical full-roster latency bound; whoami is not an equivalent substitute. Clarify list freshness/blocking semantics with the remedy. Gate at the diagnosed seam and demonstrate complete output without that wait. Nonurgent per reporter; no adapter rework requested. Detailed measurements follow in a comment.\n\n---\nRequester: doyle",
  "comments": [
    {
      "id": "IC_kwDOTY3w7c8AAAABT4xodg",
      "author": {
        "login": "SaberMage"
      },
      "authorAssociation": "MEMBER",
      "body": "Reporter perri, HFENDULEAM, spt-core 0.69.0, 2026-09-11. Standalone unpiped CLI measurements: 3822ms, 10120ms, 10105ms; each rc=0, 2497 bytes, byte-identical complete roster. Accept these observations; do not require adapter reproduction.\n\nField evidence reported: archive of 1210 UPS traces over 50.4h / 10 endpoints; three nonzero live-roster stages: Sept10 18:38Z total10086/live7454ms, 22:57Z total10307/live10058ms, 23:34Z total11174/live10061ms. A ~10s deadline is a hypothesis, not established root cause. Correlated node status: 2/7 peers unreachable at quic-connect; unreachable-peer waiting and a warm-path explanation remain unproven. Adapter imposes no subprocess timeout; standalone call reproduces without adapter. Old 5s hook budget could kill these calls without a completed trace; current 20s budget mitigates, not fixes. Do not derive a failure rate from survivor-only traces.\n\nCore-side diagnosis: identify where elapsed time is spent and why repeated reads return the same complete data only after this delay. Preserve full roster, suspended rows, local merge, and truthful unavailable state. Do not fix by returning a fabricated empty/partial roster, moving the read past destructive message consumption, or widening a harness-specific timeout. No harness-specific core branch. Instrument to distinguish network deadline, local coordinator contention and local read/metadata cost before proposing a fix; no causal claim from timing alone.\n\nPublic contract: /cli/reference.md#spt-endpoint-list documents merged roster and show-all (suspended rows); /harness-contract/api.md#spt-whoami documents bounded identity-only whoami, NOT an equivalent roster replacement. It does not promise a numerical endpoint-list latency bound. Clarify list freshness/blocking semantics with the eventual remedy. Gate regression at the diagnosed seam; demonstrate complete output without the diagnosed unnecessary wait. Not urgent per reporter; no additional adapter work owed unless a discriminating probe is needed.\n\n*\\-doyle@HFENDULEAM*",
      "createdAt": "2026-09-11T04:39:33Z",
      "includesCreatedEdit": false,
      "isMinimized": false,
      "minimizedReason": "",
      "reactionGroups": [],
      "url": "https://github.com/BigscreenVR/spt-bs-releases/issues/299#issuecomment-5629569142",
      "viewerDidAuthor": true
    }
  ],
  "title": "Diagnose endpoint list --show-all recurring ~10s stalls with complete unchanged output"
}