fixup! Add new C coding style guide

Author: bettio

C_CODING_STYLE.md

@@ -901,6 +901,7 @@ typedef struct
   size_t count_spaces(const char *str);
   bool starts_with(const char *str, const char *prefix);
   ```
+
 - **Conversely**: `parse_iso8601_buf()` needs `_buf` suffix when parsing from a buffer
 
 #### Module Prefixing [AVMCCS-N017]
@@ -1096,14 +1097,17 @@ func(target, inputs, outputs, options, environment)
 #### Parameter Types
 
 1. **target**: The primary parameter being operated on (must be initialized)
+
    ```c
    bool date_time_is_valid(const DateTime *dt);
    void date_time_add_days(DateTime *dt, int days);
    void buffer_append(Buffer *buf, const char *data);
    ```
+
    Exception: `_init` and `_create` functions initialize the target parameter
 
 2. **inputs**: Additional input data with `const` qualification
+
    ```c
    // Arrays/buffers must always be followed by their length
    void hash_update(Hash *h, const uint8_t data[], size_t data_len);
@@ -1112,15 +1116,18 @@ func(target, inputs, outputs, options, environment)
    ```
 
 3. **outputs**: Usually uninitialized output parameters (come after inputs)
+
    ```c
    // Parse functions: input data first, then output location
    parse_int_result_t parse_int(const char *str, int32_t *out);
    base64_decode_result_t base64_decode(const char *encoded,
                                         uint8_t decoded[], size_t *decoded_len);
    ```
+
    Note: Additional read-write parameters may precede pure output parameters when it makes semantic sense
 
 4. **options**: Function options (prefer enums for clarity)
+
    ```c
    void user_message_show(Display *display, const char *msg,
                           user_message_style_t style);
@@ -1129,6 +1136,7 @@ func(target, inputs, outputs, options, environment)
    ```
 
 5. **environment**: Context or environment pointers (avoid globals)
+
    ```c
    void log_message(Logger *logger, const char *msg, log_level_t level,
                     Environment *env);
@@ -1899,6 +1907,7 @@ static uint32_t crc32_byte(uint32_t crc, uint8_t byte);
 Choose documentation depth based on API complexity and safety requirements:
 
 1. **Minimal**: Self-documenting functions need only brief description
+
    ```c
    /**
     * @brief Check if buffer is empty
@@ -1907,6 +1916,7 @@ Choose documentation depth based on API complexity and safety requirements:
    ```
 
 2. **Standard**: Add parameters, return values, and specific error codes [AVMCCS-D014]
+
    ```c
    /**
     * @brief Parse integer from string
@@ -1922,6 +1932,7 @@ Choose documentation depth based on API complexity and safety requirements:
    ```
 
 3. **Safety-Critical**: Add preconditions, warnings, and detailed behavior [AVMCCS-D015]
+
    ```c
    /**
     * @brief Resize dynamic buffer