Skip to content

ci: fase 1 guardrails para Aegis#2

Merged
Blackleets merged 3 commits into
mainfrom
ci/fase-1-guardrails
Jul 4, 2026
Merged

ci: fase 1 guardrails para Aegis#2
Blackleets merged 3 commits into
mainfrom
ci/fase-1-guardrails

Conversation

@Blackleets

Copy link
Copy Markdown
Owner

Resumen

  • añade Playwright smoke tests para desktop y móvil
  • añade Lighthouse CI local config
  • añade workflows de GitHub Actions para CI, Dependency Review y CodeQL
  • ignora artefactos locales de test/perf

Verificación local

  • npm run lint ✅
  • npm test ✅
  • npm run build ✅
  • npm run test:e2e ✅

Nota

Este PR aísla solo la Fase 1 de guardrails/CI y no mezcla otros cambios locales aún no preparados.

@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: bc1c870e81

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread tests/e2e/home.spec.ts Outdated

await expect(page).toHaveTitle(/AEGIS/i);
await expect(page.getByRole('heading', { name: 'AEGIS' }).first()).toBeVisible();
await expect(page.getByLabel('Open AEGIS VECTOR GPS navigation')).toBeVisible();

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Point the desktop smoke test at an existing control

Because .github/workflows/ci.yml now runs npm run test:e2e on every PR, this assertion makes the new smoke job fail even when the homepage loads: Open AEGIS VECTOR GPS navigation does not appear in the app source as label text or an aria-label (checked src/app and src/components; the only match is this test), so Playwright will wait until timeout. Please assert an existing accessible control or add this label to the UI.

Useful? React with 👍 / 👎.

Comment thread tests/e2e/mobile-home.spec.ts Outdated

await expect(page).toHaveTitle(/AEGIS/i);
await expect(page.getByRole('heading', { name: 'AEGIS' }).first()).toBeVisible();
await expect(page.getByText('CORTEX').first()).toBeVisible();

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Assert real mobile copy instead of CORTEX

Because the new CI workflow invokes the e2e suite, this mobile smoke test times out on a healthy page: CORTEX is not rendered anywhere in the app source (checked src/app and src/components; the only match is this test). Please update the assertion to text that actually exists on the mobile command surface, or add the intended copy to the UI.

Useful? React with 👍 / 👎.

@Blackleets Blackleets merged commit 5ae4f7c into main Jul 4, 2026
5 checks passed
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.

2 participants