feat(PIPE-TEST): Add Rails backend — generated by Optimus

[tarratsco]

⚠️ AI-Generated PR — This pull request was automatically generated by Optimus. All code requires human review and testing before merging.

Summary

• This work is behind a feature toggle (flipper): NO
• Auto-generated Rails backend for VA Form PIPE-TEST by Optimus AI. Engineer review required.
• New digitization — no prior vets-api controller exists for this form.
• Adds controller, model, serializer, Sidekiq job, routes, and RSpec specs.
• Team: Optimus / Aquia.

Related issue(s)

• department-of-veterans-affairs/va.gov-team#0000

Testing done

• New code is covered by unit tests
• Code generated by Optimus AI — engineer must run RSpec locally and verify controller handles happy path + validation errors before merging.
• No flipper used; feature is gated by vets-website deployment.

Screenshots

N/A

What areas of the site does it impact?

New controller at app/controllers/v0/pipe_test_controller.rb — no existing areas impacted.

Acceptance criteria

• Unit and integration tests added for controller and model
• No PII/credentials/internal URLs hardcoded
• No errors or warnings in console
• Events sent to appropriate logging solution
• No sensitive information captured in logging or specs

[va-vsp-bot]

Error: A file (or its parent directories) does not have a CODEOWNERS entry. Please update the .github/CODEOWNERS file and add the entry for the Offending file: app/controllers/v0/pipe_test_controller.rb

[github-actions]

1 Warning

⚠️

This PR changes 238 lines of code (not counting whitespace/newlines, comments, or test files). In order to ensure each PR receives the proper attention it deserves, we recommend not exceeding 200. Expect some delays getting reviews. File Summary Files app/controllers/v0/pipe_test_controller.rb (+57/-0) app/models/pipe_test_submission.rb (+69/-0) app/serializers/pipe_test_serializer.rb (+38/-0) app/sidekiq/lighthouse/submit_pipe_test_job.rb (+65/-0) config/routes/pipe_test.rb (+9/-0) Note: We exclude files matching the following when considering PR size: *.csv, *.json, *.tsv, *.txt, *.md, Gemfile.lock, app/swagger, modules/mobile/docs, spec/fixtures/, spec/support/vcr_cassettes/, modules/mobile/spec/support/vcr_cassettes/, db/seeds, modules/vaos/app/docs, modules/meb_api/app/docs, modules/appeals_api/app/swagger/, *.bru, *.pdf, modules/*/spec/fixtures/*, modules/*/spec/factories/*, modules/*/spec/**/*.rb, spec/**/*.rb, modules/*/docs/**/*.yaml, modules/*/docs/**/*.yml, modules/*/app/docs/**/*.yaml, modules/*/app/docs/**/*.yml Big PRs are difficult to review, often become stale, and cause delays.

Generated by 🚫 Danger