Assert the memory note, not the prompt's prose

`an anonymous request carries no memory note` pinned the entire default system
prompt with `==`, so hardening that prompt against model and vendor identity
leaks broke a test that has nothing to do with either. Main went red on a
change that was correct.

It now asserts what its name says: no `[From memory: ` marker for a caller we
do not recognize — the same marker the recognized-caller tests above assert the
presence of — plus that it is still the default prompt. The next wording change
will not break it, and a memory leaking into an anonymous request still will.

Deploy story

What this commit did to the running system — joined from the forge receipt chain, the part a commit page elsewhere cannot show.

pushed

by user · WAL seq 441 · 2026-08-26T08:25:10.807818Z

Changed files

• modified test/openagents_web/controllers/responses_controller_test.exs

Diff

1 file changed, +10 -1

             |> json_response(200)

      assert_receive {:recorded_request, _id, request}

      assert request.instructions == "You are OpenAgents Coder. Answer directly and concisely."

      # What this test is about: no memory rides along for a caller we do not

      # recognize. `[From memory: ` is the marker the recognized-caller tests

      # above assert the presence of.

      refute request.instructions =~ "[From memory: "

      # It is still the default prompt, asserted by the properties that prompt

      # exists to hold rather than by its prose. Pinning the whole string made

      # this test fail for a prompt edit that had nothing to do with memory.

      assert request.instructions =~ "You are OpenAgents Coder."

    end

    # The dev lane reaches this route with credentials this endpoint knows