(struct-type-info (eval 'struct:st)) fails with raco test (works with racket and drracket)

What version of Racket are you using?

6.7.0.1

What program did you run?

#lang typed/racket
(require (for-syntax racket/struct-info))

(module m typed/racket
  (provide (struct-out st))
  (struct st () #:transparent))

(require 'm)

(define vr (#%variable-reference))

(define eval-ty
  (call-with-values (λ () (eval 'struct:st
                                (variable-reference->namespace vr)))
                    (λ l l)))
(define ty (assert (car eval-ty) struct-type?))

(struct-type-info ty)

If you got an error message, please include it here.

The program fails with the following error using raco test, but otherwise works fine with racket and drracket.

raco test: "/tmp/ta.rkt"
        struct:st: contract violation
  Attempted to use a struct type reflectively in untyped code: #<struct-type:st>
  in: "struct-type/c"
  contract from: (/tmp/ta.rkt m)
  blaming: /tmp/ta.rkt
   (assuming the contract is correct)
  at: /tmp/ta.rkt:7.10
  context...:
   /nix/store/swpi9mnzfff6jv5baapa8cpr46z31p1b-racket-6.7.0.1/share/racket/collects/racket/contract/private/blame.rkt:159:0: raise-blame-error16
   /tmp/ta.rkt: [running body]

Is there any workaround to get this to work with raco test?

Context:

I need to do this for my delay-pure library, which adds non-cached pure promises to Typed Racket. The library restricts what functions can be called within a pure promise, and among other things only allows constructors for immutable structs. It works by checking the value of all free identifiers within the promise's body. When struct-constructor-procedure? returns #t for one such value, I use object-name and try to see if there is a struct type with that name within the namespace where the promise is created. I then use the information provided by struct-type-info to check whether the struct type is immutable or not (using code from Greg Hendershott's egal, ported to Typed Racket).

Start by running the /tmp/ta.rkt reproducer with raco test, then compare it with racket and drracket. Trace the interaction between eval, variable-reference->namespace, struct-type-info, and the typed/racket module boundary; done means the reproducer works consistently under raco test or a documented workaround is identified.