# **Administrator** Markdown Formatting Test _Only_ file_name

This file contains no report, patient, or clinical content. It exists only to test Markdown formatting and rendering behaviour expected to succeed.

The first heading intentionally contains bold text, italic text, and a literal underscore so the browser title can also be checked as plain text.

# Heading 1 Test

## Heading 2 Test

### Heading 3 Test

#### Heading 4 Test

##### Heading 5 Test

###### Heading 6 Test

## Heading and Fragment Edge-Case Tests

### A_B_C

This fragment link should target the literal-underscore heading above: [Jump to A_B_C](#a-b-c).

### **Formatted** [Heading](https://example.com/heading) _Test_

This fragment link should target the formatted heading above using its visible text: [Jump to formatted heading](#formatted-heading-test).

### Duplicate Heading

### Duplicate Heading

These fragment links should target the first and second duplicate headings respectively: [first duplicate](#duplicate-heading) and [second duplicate](#duplicate-heading-2).

## Paragraph and Inline Formatting Tests

Normal paragraph text.

This contains **bold text**.

This contains *italic text using asterisks*.

This contains _italic text using underscores_.

This contains ordinary text before **bold text** and ordinary text after it.

This contains ordinary text before *italic text* and ordinary text after it.

This contains ordinary text before _italic text_ and ordinary text after it.

This contains **bold text with _nested italic text_ inside it**.

This contains *italic text with **nested bold text** inside it*.

This line contains a literal underscore in a filename: file_name_with_parts.txt.

This line contains a literal underscore pattern that should stay literal: A_B_C.

This line contains an unclosed bold marker that should stay literal: **unclosed bold.

This line contains an unclosed italic marker that should stay literal: *unclosed italic.

This line contains an underscore marker that should stay literal inside a word: one_two_three.

This line tests an escaped asterisk marker that should stay literal: \*not italic\*.

This line tests an escaped underscore marker that should stay literal: \_not italic\_.

This line tests an escaped backslash that should display as one literal backslash: \\.

This line tests XML and HTML special characters as ordinary text: < > & " '.

This line tests raw HTML-looking text, which should display literally rather than execute: <script>alert("test")</script>.

This line tests common Unicode characters as ordinary text: → ← ↑ ↓ ▲ • – —.

## Multi-Line Paragraph Test

This is the first source line of one paragraph.
This is the second source line of the same paragraph.
This is the third source line of the same paragraph.

This is a separate paragraph after an empty line.

## Markdown Link Tests

This is a simple Markdown link: [Example](https://example.com/path).

This link label contains **bold text**: [**Bold link label**](https://example.com/bold).

This link label contains *italic text*: [*Italic link label*](https://example.com/italic).

This link label is itself a visible URL and should still create only one link: [https://example.com](https://example.org).

This destination contains balanced parentheses: [Balanced parentheses](https://example.com/Foo_(bar)).

This destination contains nested parentheses: [Nested parentheses](https://example.com/a(b(c)d)e).

This local destination contains parentheses: [Local parentheses](/docs/a(b)c).

This destination contains an escaped closing parenthesis: [Escaped parenthesis](https://example.com/a\)b).

This label contains an escaped closing square bracket before more text: [Label with escaped \] bracket](https://example.com/escaped-label).

This is an allowed mail link: [Mail example](mailto:test@example.com).

This is an allowed fragment link: [Fragment example](#heading-2-test).

This is an allowed root-relative link: [Root-relative example](/documents/example.html).

This is an allowed current-directory link: [Current-directory example](./example.html).

This is an allowed parent-directory link: [Parent-directory example](../example.html).

## Bare URL Tests

Simple bare URL: https://example.com/path

Bare URL followed by sentence punctuation: https://example.com/path.

Bare URL inside parentheses: (https://example.com/path).

Bare URL inside double quotes: "https://example.com/path"

Bare URL with balanced parentheses in the URL: https://example.com/Foo_(bar)

Bare URL with query and fragment text: https://example.com/path?one=1&two=2#section

HTTP is also allowed: http://example.com/path

## Bullet List Tests

- Bullet item 1
* Bullet item using an asterisk marker
+ Bullet item using a plus marker
- Bullet item with **bold text**
- Bullet item with *italic text using asterisks*
- Bullet item with _italic text using underscores_
- Bullet item with [a Markdown link](https://example.com/list)
  - Nested bullet item
	- Nested bullet item using one tab
  - Nested bullet item with **bold text**
    - Deeper nested bullet item

Normal paragraph after the bullet list.

## Numbered List Tests

1. Numbered item 1
2. Numbered item with **bold text**
3. Numbered item with *italic text using asterisks*
4. Numbered item with _italic text using underscores_
5. Numbered item with [a Markdown link](https://example.com/numbered)
  1. Nested numbered item
  2. Nested numbered item with **bold text**
    1. Deeper nested numbered item

Normal paragraph after the numbered list.

## Mixed List Tests

- Bullet parent
  1. Numbered child
  2. Numbered child with *italic text*
- Second bullet parent
  - Bullet child
    1. Numbered grandchild

1. Numbered parent
  - Bullet child
  - Bullet child with **bold text**
2. Second numbered parent

Normal paragraph after the mixed lists.

## Four-Space Preformatted Block Test

    PRE line 1
      PRE line 2 with extra indentation
        PRE line 3 with more indentation

    Characters inside this block should remain literal: **bold** _italic_ <tag> https://example.com/

Normal paragraph after the four-space preformatted block.

## Fenced Preformatted Block Tests

```text
Fence length 3.
Markdown-looking text should remain literal here:
**bold**
_italic_
[link](https://example.com/)
<script>alert("test")</script>
```

````text
Fence length 4.
A shorter run of three backticks inside this block should remain literal:
```
Still inside the four-backtick fence.
````

```text
Backtick fence length 3 with a longer closing fence.
The closing fence below has four backticks and should still close this block.
~~~~
The tilde fence-looking line above should remain literal inside this backtick block.
````

### Tilde Fence Tests

~~~text
Tilde fence length 3.
Markdown-looking text should remain literal here:
**bold**
_italic_
[link](https://example.com/)
<script>alert("test")</script>
A backtick fence-looking line should remain literal here:
```
~~~

~~~~text
Tilde fence length 4.
A shorter run of three tildes inside this block should remain literal:
~~~
Still inside the four-tilde fence.
~~~~

~~~text
Tilde fence length 3 with a longer closing fence.
The closing fence below has four tildes and should still close this block.
~~~~

Normal paragraph after the fenced blocks.

## Empty-Line and Section Transition Test

Paragraph before an empty line.

Paragraph after an empty line.

### Heading After Paragraph

Paragraph immediately following a heading.

- List after a paragraph
- Second list item

Paragraph immediately following a list.

    Preformatted block after a paragraph.

Paragraph immediately following a preformatted block.

## End of Test

If this file renders without build errors, visually inspect the HTML and DOCX outputs for the supported behaviour that applies to each format: headings and fragment targets, duplicate heading targets, multi-line paragraph grouping, inline emphasis, literal and escaped emphasis markers, special-character escaping, Unicode characters, Markdown links, bare URLs, all supported unordered-list markers, list numbering and nesting, tab-based list nesting, mixed list types, preformatted blocks, backtick and tilde fenced blocks, longer valid closing fences, mixed fence characters remaining literal, literal code-block content, and paragraph/block transitions. For HTML, also inspect browser title text.

This file is the shared successful rendering baseline for the current HTML and DOCX exporters. Format-specific presentation may differ, but the supported Markdown interpretation should remain aligned where the behaviour has a meaningful equivalent in both formats.