Skip to content

fix(test): run ecosystem through trusted-peer custom server - #14403

Merged
diegosouzapw merged 1 commit into
release/v3.8.51from
fix/qg08-ecosystem-peer-context-20260921
Sep 24, 2026
Merged

diegosouzapw merged 1 commit into
release/v3.8.51from
fix/qg08-ecosystem-peer-context-20260921

Conversation

@diegosouzapw

@diegosouzapw diegosouzapw commented Sep 21, 2026 •

Copy link
Copy Markdown
Owner

Full candidate CI 35664744712 found 16 ecosystem failures, including unauthenticated management setup and disabled A2A. The ecosystem harness still booted bare next dev; the production authorization pipeline requires the custom server TCP peer stamp for loopback bootstrap. Match the existing protocol-client harness using run-next.mjs and loopback binding. Production authorization remains unchanged.

The real harness subprocess regression fails on the old entrypoint and passes after the change. Hooks pass. This focused process-boundary proof is not yet full live ecosystem acceptance; rerun the real suite on the integrated candidate before merge. Stacked on the recovery candidate.

Resgate para release/v3.8.51 (merge-batch 2026-09-23)

Esta PR estava empilhada sobre test/qg-recovery-candidate-20260921, um branch sem PR que não vai para a release. A base foi trocada para release/v3.8.51 e o branch foi reconstruído a partir do tip da release (01d2af91).

  • Carregado: 6b4c5d18 "fix(test): boot ecosystem through trusted-peer server", re-aplicado sem conflitos como 8dbfdfbf (o único commit próprio desta PR).
  • Ficou na pilha: todos os commits de test/qg-recovery-candidate-20260921.
  • Diff final contra a release: 2 arquivos. scripts/dev/run-ecosystem-tests.mjs sobe run-next.mjs com HOST=127.0.0.1 em vez de run-next-playwright.mjs. O teste novo é tests/unit/build/ecosystem-server-entrypoint.test.ts.
  • Validação (red→green):
    • Com o fix, o teste de subprocesso passa (1/1).
    • Com o run-ecosystem-tests.mjs do tip, falha com Cannot find module …/scripts/dev/run-next-playwright.mjs (exit 1 ≠ 0).
    • npm run test:ecosystem completo não rodou no devbox, porque a carga ficou entre 20 e 68 durante a sessão (limite de 10). Quem valida é o job de CI test-ecosystem.
  • Fragilidade observada: com load de aproximadamente 40, o prazo ECOSYSTEM_SERVER_WAIT_MS=4000 do teste estourou. O run-ecosystem-tests.mjs saiu por main().catch sem matar o servidor fixture, e o processo órfão segurou o node --test aberto até ser morto à mão. Em runner de CI (carga baixa) isso não ocorre.

@diegosouzapw
diegosouzapw changed the base branch from test/qg-recovery-candidate-20260921 to release/v3.8.51 September 24, 2026 00:58
@diegosouzapw
diegosouzapw force-pushed the fix/qg08-ecosystem-peer-context-20260921 branch from 6b4c5d1 to 8dbfdfb Compare September 24, 2026 00:59
@diegosouzapw
diegosouzapw marked this pull request as ready for review September 24, 2026 00:59
diegosouzapw added a commit that referenced this pull request Sep 24, 2026
) (#14415)

Merge-batch 2026-09-23 (PRs do mantenedor, Trilha B, retrabalhada).

Um worker corrigiu o defeito apontado na revisão direto no branch da PR; o detalhe está na seção "Rework (merge-batch 2026-09-23)" do corpo, com a prova de red→green. Revalidado numa árvore combinada das PRs da 2ª leva da Trilha B (#14415 #14472 #14468 #14493 #14403) sobre o tip atual de `release/v3.8.51`:
- 104/104 testes node focados + 46/46 vitest (as 6 suítes de UI que saíram da quarentena); `check:provider-consistency` OK (359)
- `typecheck:core`: só o herdado `cliproxyAccountHealth.ts:157`; `check:open-sse-typecheck`: só o herdado `auggie.ts` (base-red #14547, corrigido pela #14511)
- eslint nos arquivos alterados limpo; file-size OK
diegosouzapw added a commit that referenced this pull request Sep 24, 2026
…h a one-shot bootstrap token (#14296) (#14472)

Merge-batch 2026-09-23 (PRs do mantenedor, Trilha B, retrabalhada).

Um worker corrigiu o defeito apontado na revisão direto no branch da PR; o detalhe está na seção "Rework (merge-batch 2026-09-23)" do corpo, com a prova de red→green. Revalidado numa árvore combinada das PRs da 2ª leva da Trilha B (#14415 #14472 #14468 #14493 #14403) sobre o tip atual de `release/v3.8.51`:
- 104/104 testes node focados + 46/46 vitest (as 6 suítes de UI que saíram da quarentena); `check:provider-consistency` OK (359)
- `typecheck:core`: só o herdado `cliproxyAccountHealth.ts:157`; `check:open-sse-typecheck`: só o herdado `auggie.ts` (base-red #14547, corrigido pela #14511)
- eslint nos arquivos alterados limpo; file-size OK
diegosouzapw added a commit that referenced this pull request Sep 24, 2026
Merge-batch 2026-09-23 (PRs do mantenedor, Trilha B, retrabalhada).

Um worker corrigiu o defeito apontado na revisão direto no branch da PR; o detalhe está na seção "Rework (merge-batch 2026-09-23)" do corpo, com a prova de red→green. Revalidado numa árvore combinada das PRs da 2ª leva da Trilha B (#14415 #14472 #14468 #14493 #14403) sobre o tip atual de `release/v3.8.51`:
- 104/104 testes node focados + 46/46 vitest (as 6 suítes de UI que saíram da quarentena); `check:provider-consistency` OK (359)
- `typecheck:core`: só o herdado `cliproxyAccountHealth.ts:157`; `check:open-sse-typecheck`: só o herdado `auggie.ts` (base-red #14547, corrigido pela #14511)
- eslint nos arquivos alterados limpo; file-size OK
diegosouzapw added a commit that referenced this pull request Sep 24, 2026
Merge-batch 2026-09-23 (PRs do mantenedor, Trilha B, retrabalhada).

Um worker corrigiu o defeito apontado na revisão direto no branch da PR; o detalhe está na seção "Rework (merge-batch 2026-09-23)" do corpo, com a prova de red→green. Revalidado numa árvore combinada das PRs da 2ª leva da Trilha B (#14415 #14472 #14468 #14493 #14403) sobre o tip atual de `release/v3.8.51`:
- 104/104 testes node focados + 46/46 vitest (as 6 suítes de UI que saíram da quarentena); `check:provider-consistency` OK (359)
- `typecheck:core`: só o herdado `cliproxyAccountHealth.ts:157`; `check:open-sse-typecheck`: só o herdado `auggie.ts` (base-red #14547, corrigido pela #14511)
- eslint nos arquivos alterados limpo; file-size OK
@diegosouzapw
diegosouzapw merged commit db70929 into release/v3.8.51 Sep 24, 2026
9 of 20 checks passed
diegosouzapw added a commit that referenced this pull request Sep 24, 2026
The suite seeds a provider node and mints an API key via the management API in
open bootstrap mode. That window stays open only for a loopback peer, and
locality comes from the TCP-peer stamp that only the custom server in
run-next.mjs writes. Booted through run-next-playwright.mjs (bare next dev) it
got 401 on POST /api/provider-nodes before any assertion ran - red on the
release tip db70929 on the idle .113, also before #14472.

Same trap #11535 and #14403 fixed in the protocol and ecosystem harnesses.
Integration only runs on the release PR, so a unit source-contract test now pins
the boot target where every PR sees it. Fixed suite: 2/2 green on the same box.

Refs #14547
diegosouzapw added a commit that referenced this pull request Sep 25, 2026
The suite seeds a provider node and mints an API key via the management API in
open bootstrap mode. That window stays open only for a loopback peer, and
locality comes from the TCP-peer stamp that only the custom server in
run-next.mjs writes. Booted through run-next-playwright.mjs (bare next dev) it
got 401 on POST /api/provider-nodes before any assertion ran - red on the
release tip db70929 on the idle .113, also before #14472.

Same trap #11535 and #14403 fixed in the protocol and ecosystem harnesses.
Integration only runs on the release PR, so a unit source-contract test now pins
the boot target where every PR sees it. Fixed suite: 2/2 green on the same box.

Refs #14547
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant