docs: the CI/CD link in frontend-testing.md opens the E2E section

[HardMax71]

Summary

Small docs fix found while building the docs for #407. The "See CI/CD" link at the end of frontend-testing.md points at cicd.md#stack-tests, an anchor that cicd.md no longer has, so it opens the top of the page. mkdocs only reports it at INFO, so --strict builds pass.

Changes

The link points at #e2e, the slug of cicd.md's ### E2E heading.

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Refactoring (no functional changes)
• CI/CD or tooling changes

Test Plan

• Backend unit tests pass (cd backend && uv run pytest tests/unit)
• Frontend unit tests pass (cd frontend && npm run test)
• Backend E2E tests pass (docker compose exec -T backend sh -c 'uv sync --group test --no-dev --frozen --no-install-project --no-build && pytest tests/e2e')
• Frontend E2E tests pass (cd frontend && npm run test:e2e)
• API spec and client regenerated if routes or schemas changed (./deploy.sh openapi, then ./deploy.sh types), never edited by hand
• Manual testing performed

Validation: CI's docs command (mkdocs build --strict with mkdocs 1.6.1 and mkdocs-material 9.7.7) exits 0, and the "does not contain an anchor '#stack-tests'" line is gone.

Checklist

• My code follows the project's style guidelines
• I have run pre-commit run --all-files and all checks pass
• I have added tests that prove my fix/feature works
• I have updated documentation if needed
• My changes don't introduce new warnings

---

Summary by cubic

Fixes the CI/CD link in frontend-testing.md so it opens the E2E section instead of the top of the page.

^{Written for commit 9bc291c. Summary will update on new commits.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud