OpenAI wrapper service review

[lakshay6666]

Summary

Adds an OpenAI wrapper service for issue #11.

The service is located under services/openai-wrapper-service and includes:

• REST endpoints for /generate and /health
• generated OpenAPI spec
• CLI command for text generation
• Dockerfile and Docker build target
• service Makefile targets
• GitHub CI workflow
• README with setup, API key config, and minimal hardware requirements
• tests with fake adapters, so no OpenAI API calls are made during tests

Notes

The service uses the official OpenAI Python SDK. The API key is read from OPENAI_API_KEY at runtime and is not stored in the repo.

Validation

• make lint
• make test
• make generate-openapi

Closes #11

[plc-dev]

General comments:

• Preferably use conventional commits to format commit messages, even if not strictly enforced yet by the repo.
• Create branches that relate to the issue (e.g. by using the provided button within the Github-UI. See
  and

• Do not create multiple branches per issue. If required, delete stale ones (codex/openai-wrapper-service-review and codex/openai-wrapper-service)
• There's not necessarily something wrong with using AI to create code, but:
  • make sure you understand the code that was generated, by first reviewing it yourself
  • and before that, ensure that all the requirements have been specified. If you find the issue description is too ambiguous, ask for clarifications by the person who created the issue. If you forego understanding the requirements of the feature, the AI will just produce something anyways, which you then can not validate. This shifts all the effort to the person reviewing the code, which defeats the entire purpose ¯_(ツ)_/¯