Build with an AI agent

Add a server-side Adapt-1 integration to this repository.

First inspect the language, framework, package manager, test runner,
environment-variable conventions, and server/client boundary.

Read:
- https://docs.reilabs.org/docs/neuroadapt/quickstart.md
- https://docs.reilabs.org/docs/neuroadapt/request-contracts.md
- https://docs.reilabs.org/neuroadapt-openapi.json
- https://docs.reilabs.org/docs/neuroadapt/errors-and-reliability.md

Implement:
- Follow the repository's existing HTTP-client and error-handling patterns.
- Read ADAPT1_API_KEY from the server environment; never expose or log it.
- Default ADAPT1_BASE_URL to
  https://rei-neuroadapt-api.reilabs.org/api/v1.
- Add one function accepting a nonempty message and sending
  POST {baseUrl}/memory/query with:
  {
    "session_id": "ignored",
    "user_message": <the caller's message>,
    "top_k": 5,
    "include_reasoning": true,
    "update_memory_state": false
  }
- Send Authorization: Bearer <ADAPT1_API_KEY> and JSON content type.
- Validate the request against MemoryQueryRequest and validate the response
  fields the application consumes. Do not fabricate a response model.
- Add a finite timeout and useful errors for missing configuration, non-2xx
  status, malformed JSON, unexpected shape, and transport failure.
- Return the structured result directly.
- Add placeholder variable names to .env.example.
- Test with mocked HTTP. Do not call live services or write persistent state.
- Include a short application usage example.

Run the repository's relevant formatting, linting, type checks, and tests.
Report the files changed, commands run, and results. Identify assumptions
and untested behavior explicitly. Do not make unrelated changes.

Application requirement:
[Describe the API route, server action, job, or CLI that should use the result.]

Extend this repository with one Adapt-1 learning workflow.

Read:
- https://docs.reilabs.org/docs/adapt-1/getting-started.md
- https://docs.reilabs.org/docs/neuroadapt/first-learned-result.md
- https://docs.reilabs.org/docs/neuroadapt/request-contracts.md
- https://docs.reilabs.org/docs/neuroadapt/discovery-transition-projection.md
- https://docs.reilabs.org/neuroadapt-openapi.json
- https://docs.reilabs.org/docs/neuroadapt/errors-and-reliability.md

Before implementation:
- Describe the result, inputs available before it, observable target/outcome,
  Domain scope, and state lifecycle for the application requirement below.
- Use the first-learned-result tutorial only if an observation-to-target
  prediction is the right relationship. Otherwise select the relevant
  documented feedback, sequential, or trajectory guide.
- The checked-in OpenAPI snapshot is incomplete for Domain learning and
  trajectory workflows. Identify guide-documented fields missing from it.
  Do not invent fields or delete essential learning configuration merely
  to match that incomplete snapshot. Report actual source conflicts.

Implement one complete loop:
- Keep API calls and ADAPT1_API_KEY on the server.
- Use a fresh Domain for an independent test; persist its ID for reconnecting.
- Supply only information available before the requested result. Withhold
  the target at prediction time; do not insert a solved policy or answer.
- Preserve request intent before writes and sanitized responses afterward.
- Check transport success and learner admission separately.
- Handle accumulating state, missing diagnostics, and abstention explicitly.
- Consume the actual route-defined result.
- Inspect the later result and applicable learner-state diagnostics.
- Never automatically retry ambiguous writes or reset existing state.
- Mock the network in automated tests. Do not make live writes without
  explicit authorization and a dedicated test credential.

Run the repository's relevant checks. Report which parts were schema-checked,
which follow the written guides, which were mock-tested, and which were
actually live-tested. Do not claim live behavior from a mocked response.

Application requirement:
[Describe the result and the observations or outcomes your application owns.]