docs(readme): document distant headers and flexible formats

Update the README to reflect the parser's new, more flexible header-matching capabilities.

This change documents two key features recently added to the parser:
-   **Distant Headers:** Clarifies that content-related headers (`File:`, `Append File:`, etc.) are now associated with the *next available* code block, allowing for descriptive paragraphs between a header and its code.
-   **Flexible Hash Formats:** Updates the examples to show that headers can use more than two hash symbols (`###`, `####`) and can include descriptive text before the action keyword (e.g., `### The Main File: ...`).

A new "Distant / Flexible Header" example has been added to explicitly demonstrate this enhanced functionality to users.

Author: Romelium

README.md

@@ -14,6 +14,7 @@ The tool reads a markdown file, identifies actions (like creating, appending, pr
 * Supports appending content to existing files (creates if not exists).
 * Supports prepending content to existing files (creates if not exists).
 * Supports deleting files.
+* Flexible association of headers with code blocks, allowing for descriptive text in between.
 * Supports moving files.
 * Multiple header formats for defining actions (Markdown headers, backticks, internal comments).
 * "Wrapped" header format for associating headers with subsequent code blocks or for standalone delete/move actions.
@@ -83,10 +84,11 @@ The following header formats are recognized:
 
 **1. `File` Actions (Create/Overwrite):**
 
-These headers must be immediately followed by a fenced code block (e.g., `````, ```` ``` ````). The content of the code block becomes the content of the file.
+These headers are associated with the next available fenced code block (e.g., `````, ```` ``` ````). While they are typically placed immediately before the code block, they can be separated by paragraphs of text. The content of the associated code block becomes the content of the file.
 
 * **Markdown Headers:**
-  * `## File: path/to/your/file.txt`
+  * `## File: path/to/your/file.txt` (and with more hashes like `###`, `####`, etc.)
+  * `### Any descriptive text File: path/to/your/file.txt`
   * `**File: path/to/your/file.txt**`
 * **Backtick Path Only:** (Implies `File` action)
   * `` `path/to/your/file.txt` ``