SREDSimplify Engineering

Appearance

Tooling Reference ​

Repo Helpers ​

Startup ​

  • start.sh: starts frontend, Spring Boot backend, and python service using Doppler-injected environments.
  • start.sh requires an interactive terminal and gum.
  • Pressing Ctrl+C in the start.sh terminal stops and attempts to clean up processes started in that run.

Validation and E2E scripts ​

  • scripts/e2e_backend_comprehensive.sh: runs the backend business E2E suite.
  • scripts/check_expert_review_env.sh: validates required Doppler secrets for expert-review linked testing.
  • scripts/e2e_expert_review_flow.sh: expert review flow specific test runner.
  • scripts/e2e_full_flow.sh: broader scripted flow runner.

Operational scripts ​

  • scripts/configcat_sync.py: sync helper for ConfigCat settings from repo-managed configuration inputs.
  • scripts/inject_frontmatter.sh: helper for adding or normalizing markdown frontmatter.

GitHub Actions Workflows ​

Verification ​

  • .github/workflows/quick-check.yml: fast non-main branch feedback for frontend lint/typecheck, Java compile, and Python syntax-class linting.
  • .github/workflows/ci.yml: main branch and PR validation across frontend, Java, Python, and backend E2E.
  • .github/workflows/docs-ci.yml: canonical docs CI — on pull requests to main that touch docs/** or docs workflow files, runs npm ci and npm run docs:build in docs/ (see workflow file for exact path filters).
  • .github/workflows/security.yml: scheduled and PR security scanning for dependencies, images, and secrets.
  • .github/workflows/gh-aw-validate.yml: validates and recompiles gh-aw Markdown workflows to keep .lock.yml files in sync.

Deployment ​

  • .github/workflows/release-manager.yml: computes the next semantic version from Conventional Commits for main pushes that touch backend deploy assets (backend/**, docker-compose.yml), creates the git tag, and creates the GitHub Release placeholder.
  • .github/workflows/deploy.yml: tag-gated production release workflow for backend services only.
  • .github/workflows/label-sync.yml: upserts repository labels used by issue triage, release, and automation workflows.

Docs publishing (production): .github/workflows/docs-deploy.yml is the production path for the public docs site. It builds docs/ and publishes .vitepress/dist to the sredsimplify-docs Cloudflare Pages project via direct upload. The preferred CI credential is CLOUDFLARE_API_TOKEN; the Wrangler OAuth secret pair exists only as a fallback while a long-lived API token is being provisioned. Cloudflare Pages Git-triggered deployments should remain disabled for this project; if docs are stale in production, inspect this workflow first.

Source of truth hierarchy: use AGENTS.md at the repository root for release and validation commands; use this Tooling reference for workflow file paths and scripts; use runbooks under /ops/ for incident response.

Agent and automation workflows ​

  • .github/workflows/aw-ci-failure-investigator.md
  • .github/workflows/aw-dependency-update.md
  • .github/workflows/aw-docs-maintainer.md
  • .github/workflows/aw-issue-triage.md
  • .github/workflows/aw-pr-review.md
  • .github/workflows/aw-release-notes.md
  • .github/workflows/claude.yml
  • .github/workflows/claude-code-review.yml

Treat those as automation surfaces, not core app runtime.

Environment and Config Sources ​

  • Local helper scripts expect Doppler for secrets injection.
  • start.sh additionally expects gum for terminal interaction and status rendering.
  • Deploy workflows generate .env files from Doppler at deploy time.
  • Application release deploys are triggered by semantic version tags, while .github/workflows/release-manager.yml only evaluates main pushes that touch backend deploy assets.
  • COPILOT_GITHUB_TOKEN is used by the release manager because tags created with the default GITHUB_TOKEN do not reliably fan out to downstream deployment workflows.
  • docker-compose.yml is a deploy-time compose file for prebuilt images, not a dev compose file.

Canonical Docs For Each Concern ​