fix(http): remove implementation limit recommendations

Specific minimum sizes are intentionally left unspecified. Implementations operate in diverse environments with varying constraints, so limits are implementation-defined.

Making operations fallible with size-exceeded is sufficient
to ensure correct error handling without prescribing
specific thresholds.

Author: ricochet

proposals/cli/wit-0.3.0-draft/deps.lock

@@ -10,10 +10,10 @@ sha512 = "19f4eb8fa62e96ba37b3ea231af6a3bc396c28f82935018a3322441321936b34fb0e44
 
 [random]
 path = "../../random/wit-0.3.0-draft"
-sha256 = "5794796c909d6656fcbae6bed28265210ca57308a624119ac0a472326a75aa8f"
-sha512 = "812ce57aa13ff3128779d41f4dad50714365e4f9cfd2e1b13458a885fa65da05e409f145deefa25c4a82e0e301a41e2e6572705b35752dc33908d565a73a2e9c"
+sha256 = "2d54fe2815781a7462f3540b0959842b7e15d9fe8530c2b961b35451b6922670"
+sha512 = "ac1a04d180f8aa11ac82529a0de7ff01c8d51d10424806aefe1c1d52ea9ade9911eaee2b3f7d9c23f4b3bfdff469af6482f4a9e5b800c465b9fb7b73ccc635c7"
 
 [sockets]
 path = "../../sockets/wit-0.3.0-draft"
-sha256 = "0be70fab90ec1d62e620f37f8fc55397222ceb68ca8387eb0503df7173782634"
-sha512 = "997e336258dd3d8d1bf1b27463e77d1dc2160eb13fff899c93b446973f5efbc59448a23279b60568679c08e006a20cc88769ec74d6d30baa4e7a17df0bdb2c30"
+sha256 = "5e7010b31fc80b5484cdcad7bfaae9dbb2134d3debfa6a90c69c30ec8cf7d55e"
+sha512 = "3863bd53d4ef1815f0f0f48d4032e3232322a3dbfa875eb573df2940264aacfe55d672886323406e5942ffc38ed5ad7dce91fcff3ff1e2e072773bb6dd9c7cd1"

proposals/http/wit-0.3.0-draft/deps.lock

@@ -14,8 +14,8 @@ sha256 = "8808ea3adfbc1a025d649b82ddf4f38232ca4377100cfe671d80d5ee37fa3147"
 sha512 = "19f4eb8fa62e96ba37b3ea231af6a3bc396c28f82935018a3322441321936b34fb0e44360b378145fcb681d9fea810745969d8baab02ae6017be1784be8abe45"
 
 [random]
-sha256 = "5794796c909d6656fcbae6bed28265210ca57308a624119ac0a472326a75aa8f"
-sha512 = "812ce57aa13ff3128779d41f4dad50714365e4f9cfd2e1b13458a885fa65da05e409f145deefa25c4a82e0e301a41e2e6572705b35752dc33908d565a73a2e9c"
+sha256 = "e51ca727c7bbc0f5b6d7e52bb68d5d838a1c8f3d3ae683cf1c0f247b91b0633f"
+sha512 = "77791400acebdea60c35a3ca455ad73bc64584840a42fb2365bcfee6cff835fb14fb625145cdbde6cb7a153c841b479393dde8aa0f21bc7bab7046aca541aefb"
 
 [sockets]
 sha256 = "0be70fab90ec1d62e620f37f8fc55397222ceb68ca8387eb0503df7173782634"

proposals/http/wit-0.3.0-draft/types.wit

@@ -121,11 +121,6 @@ interface types {
     /// implementation-defined limit on field sizes. This may apply to
     /// an individual `field-value`, a single `field-name` plus all its
     /// values, or the total aggregate size of all fields.
-    ///
-    /// Implementations MUST accept individual field values of at least
-    /// 8192 bytes and total aggregate field sections of at least 16384
-    /// bytes. These minimums ensure portability across common HTTP
-    /// servers and match HTTP/2's minimum SETTINGS_MAX_FRAME_SIZE.
     size-exceeded,
 
     /// This is a catch-all error for anything that doesn't fit cleanly into a
@@ -188,9 +183,7 @@ interface types {
   ///
   /// Implementations may impose limits on individual field values and on total
   /// aggregate field section size. Operations that would exceed these limits
-  /// fail with `header-error.size-exceeded`. Implementations MUST accept
-  /// individual field values of at least 8192 bytes and total aggregate field
-  /// sections of at least 16384 bytes.
+  /// fail with `header-error.size-exceeded`
   @since(version = 0.3.0-rc-2026-02-09)
   resource fields {