rust-rest VS awint

Overview: I'm trying to write a simple REST API that lets you add or read messages from a HashMap on the server. To use this HashMap with Rocket I need to let Rocket manage its state. The compiler is demanding an implementation of a FromRequest trait on the state when it shouldn't be. (Notably, the implementation I'm borrowing from on GitHub doesn't have one at all).

Additionally as far as I am aware, this is the first biginteger library to use what I think is called "separated storage and reference types". Similar to the way that Rust has storage types like [T; N], Vec , and String and reference types like [T] and str, my library has the storage types ExtAwi and InlAwi, with the common reference type being Bits. Bits uses some DST magic to achieve only single pointer indirection while being able to take advantages of Rust's mutable and immutable reference mechanics. Parts of the crate are admittedly hacks and use a lot of unsafe to achieve these things performantly, but I have a drawn on my previous numerical fuzzing experience and built a huge test suite (see `testcrate` in my repo) with purpose built tests for every function that is run under MIRI, debug mode with plenty of debug assertions, and release mode with a large number of iterations.

I just published my awint system of crates today. I have a no_alloc_test crate in the repository that builds and links the main crate to make sure that no dependency on an allocator is brought in (building the main crate is not enough, it seems that the checks for an allocator only occurs when linking to a building binary). When I follow the exact sequence of instructions that the `no_alloc_build` job in the `.github/workflow` file takes, it works first time on a local machine (specifically, Debian WSL 2 with a freshly downloaded rustup), but it fails with linking errors on the Actions CI run. How do I debug this issue?