Summary
scripts/e2e/run-real-e2e-lane.sh currently defaults to every playwright.real.config.ts testMatch spec. On the 2026-09-09 huawei-dev real stack at 2090a420, the full lane produced 7 passed / 17 failed and manifest status failed, while the supported Golden Flows target (AGENTHUB_E2E_SPEC_TARGET=golden-flows.spec.ts) passed 4/4.
The full-lane failures mix two categories; this issue tracks the stale legacy lane rather than a product regression.
Verified causes
app/e2e/chat-real.spec.ts direct API tests still mint a hard-coded local JWT (agenthub-local-dev-secret-key-32chars-min) and expect the legacy Hub envelope code: "OK" / old Edge health envelope. Current Hub returns lowercase ok; current Edge health is flat (status, http_status), and direct Hub APIs use real Hub sessions.
- With a fresh non-dev Edge process, the auto-generated local auth token made Hub→Edge and direct Edge API requests 401. The huawei-dev restart script was missing
AGENTHUB_DEV=1; fixing that restored GF4 and Edge API access.
- The
chat-real browser flow also selected the composer <form> instead of its textbox.
- Running
real-oidc-login.spec.ts concurrently with the rest hit TokenDance ID rate limiting (too many requests); this is separate from the stale direct-API assertions.
Acceptance
Evidence
- Full lane manifest:
/root/agenthub-dev/AgentHub/tests/artifacts/manifest-20260909-073510.json (failed)
- Targeted Golden Flows manifest:
/root/agenthub-dev/AgentHub/tests/artifacts/manifest-20260909-073823.json (passed, 4/4)
- Current source:
2090a420f733f14accc6036175145f6b9d8874c2
Summary
scripts/e2e/run-real-e2e-lane.shcurrently defaults to everyplaywright.real.config.tstestMatch spec. On the 2026-09-09 huawei-dev real stack at2090a420, the full lane produced7 passed / 17 failedand manifest statusfailed, while the supported Golden Flows target (AGENTHUB_E2E_SPEC_TARGET=golden-flows.spec.ts) passed4/4.The full-lane failures mix two categories; this issue tracks the stale legacy lane rather than a product regression.
Verified causes
app/e2e/chat-real.spec.tsdirect API tests still mint a hard-coded local JWT (agenthub-local-dev-secret-key-32chars-min) and expect the legacy Hub envelopecode: "OK"/ old Edge health envelope. Current Hub returns lowercaseok; current Edge health is flat (status,http_status), and direct Hub APIs use real Hub sessions.AGENTHUB_DEV=1; fixing that restored GF4 and Edge API access.chat-realbrowser flow also selected the composer<form>instead of its textbox.real-oidc-login.spec.tsconcurrently with the rest hit TokenDance ID rate limiting (too many requests); this is separate from the stale direct-API assertions.Acceptance
chat-real.spec.tsdirect API tests are retired, rewritten to use real OIDC/Hub sessions, or split into a separate explicitly-supported lane.OK/Edge-envelope assumptions from any retained tests.failedmanifest.Evidence
/root/agenthub-dev/AgentHub/tests/artifacts/manifest-20260909-073510.json(failed)/root/agenthub-dev/AgentHub/tests/artifacts/manifest-20260909-073823.json(passed, 4/4)2090a420f733f14accc6036175145f6b9d8874c2