assertNull(pc.getPassword());
        verify(spyAuth, times(1)).getPasswordAsCharArray();
    }

    @Test
    @DisplayName("clone: copies fields and cached subject; instances are independent")
    void testCloneCopiesFieldsAndIndependence() throws Exception {
        // Use configuration-based constructor to also exercise copying of configuration/service fields

É isso que vamos resolver: vamos carregar o modelo antes de as requisições serem tratadas, mas apenas um pouco antes de a aplicação começar a receber requisições, não enquanto o código estiver sendo carregado.

        assertEquals(original.getUsername(), cloned.getUsername());
        assertEquals(original.getPassword(), cloned.getPassword());

        // Verify password arrays are independent
        original.secureWipePassword();
        assertNull(original.getPassword());
        assertEquals("ClonePass123!", cloned.getPassword());
    }

    /**

        // Create a copy
        DataStoreParams copy = dataStoreParams.newInstance();

        // Modify original
        dataStoreParams.put("key5", "value5");

        // Verify copy is independent
        assertTrue(dataStoreParams.containsKey("key5"));
        assertFalse(copy.containsKey("key5"));

        // Get as map and verify
        Map<String, Object> map = dataStoreParams.asMap();

That's what we'll solve, let's load the model before the requests are handled, but only right before the application starts receiving requests, not while  the code is being loaded.

## Lifespan { #lifespan }

    void testInstantiation() {
        TestLocking t = new TestLocking();
        assertNotNull(t, "TestLocking instance should not be null");
    }

    @Test
    @DisplayName("Field values are independent across instances")
    void testIndependentInstances() {
        TestLocking t1 = new TestLocking();
        TestLocking t2 = new TestLocking();

        // Set different values
        t1.numThreads = 2;

covered by this License; they are outside its scope.  The act of
running a program using the Library is not restricted, and output from
such a program is covered only if its contents constitute a work based
on the Library (independent of the use of the Library in a tool for
writing it).  Whether that is true depends on what the Library does
and what the program that uses the Library does.

  1. You may copy and distribute verbatim copies of the Library's

            assertEquals(message, e.getMessage());
        }
    }

    @Test
    public void test_multipleExceptionInstances() {
        // Test multiple instances are independent
        InvalidAccessTokenException exception1 = new InvalidAccessTokenException("Type1", "Message1");
        InvalidAccessTokenException exception2 = new InvalidAccessTokenException("Type2", "Message2");

        SmbNegotiation anotherNegotiation =
                new SmbNegotiation(anotherRequest, anotherResponse, anotherRequestBuffer, anotherResponseBuffer);

        // Verify the instances are independent
        assertNotSame(negotiation.getRequest(), anotherNegotiation.getRequest());
        assertNotSame(negotiation.getResponse(), anotherNegotiation.getResponse());

This also means that with `StreamingResponse` you have the **freedom** and **responsibility** to produce and encode the data bytes exactly as you need them to be sent, independent of the type annotations. 🤓

### Stream Bytes { #stream-bytes }

One of the main use cases would be to stream `bytes` instead of strings, you can of course do it.