Update docs (#85)

Author: DmitryBorisov-sm

.env.example

@@ -1,3 +1,6 @@
 CONDUCTOR_SERVER_URL=""
+
 CONDUCTOR_AUTH_KEY=""
-CONDUCTOR_AUTH_SECRET=""
+CONDUCTOR_AUTH_SECRET=""
+
+CONDUCTOR_MAX_HTTP2_CONNECTIONS=

DECISIONS.md

@@ -15,18 +15,6 @@ I would suggest we maintain CJS compat for now, in the hope that there's either
 
 Because it's relatively simple to support interop between ESM and CJS, and the wide footprint.
 
-
-### Using `node-fetch`
-
-who: @nicktomlin
-
-I initially explored [`undici`](https://github.com/nodejs/undici) as a way of using the built-in `fetch` support in node.
-
-Unfortunately, at the time of writing there's no clean way to handle `tls` options. Additionally, `fetch` is experimental for node 16.x which results in warnings.
-
-At some point in the future, it would be nice to migrate over once undici's `fetch` implementation is a little more feature rich and things have stabalized.
-
-
 ### Using `jest` for testing
 
 `jest` can be a little magical, but it's relatively fast (with 28.x especially), ergonomic, and provides a simple maintenance story over a BYO setup.
@@ -38,3 +26,15 @@ I considered `mocha` and `ava` (which i've also used and like) but `jest` struck
 who: @nicktomlin
 
 Typescript publication can be a wacky process and `tsup` simplifies a lot of this. 
+
+### Using `undici` to make http2 requests (if possible)
+
+who: @dmitryborisov-sm
+
+Since Node.js uses Undici for its built-in fetch functionality, Undici supports HTTP/2 and meets all our requirements. If Undici fails to initialize, the SDK will fall back to the default fetch: HTTP/1.1 in Node 18 and HTTP/2 in browsers. It's also possible to provide a custom fetch function when creating the SDK, so in theory, the SDK could work on older Node versions using libraries like node-fetch.
+
+### OpenAPI generated code should not be modified directly
+
+who: @dmitryborisov-sm
+
+The SDK should follow a layered architecture, with all modifications made in the top layers. This approach enables easy updates to autogenerated code and ensures alignment with API changes, minimizing both effort and risk.