improve TCs markdown format

[olexandr13]

We have md file format description: https://docs.testomat.io/project/import-export/export-tests/classical-tests-markdown-format/#classical-tests-markdown-format

And we refer to this format in multiple, skills, e.g. skills/generate-cases/references/test-case-format.md.

Need to:
1.

• add pre-conditions section
• reduce amount of "examples", but leave everything important
• fix amount of ### sybmols in headings (make sure generated file aligns with template requirements)
• fix davert comments (in a separate comment below)

2. Check that when you export cases from Testomat to markdown, the ouput file format aligns with the format described in file https://docs.testomat.io/project/import-export/export-tests/classical-tests-markdown-format/#classical-tests-markdown-format.
   Find and fix any differences.

3. Changes should be applied to:

• documentation under https://docs.testomat.io/project/import-export/export-tests/classical-tests-markdown-format/#classical-tests-markdown-format
• references files in all the skills where this reference used

[olexandr13]

[18.05.2026 02:50] Michael Bodnarchuk: Але були і проблемки в скілах:

1. File format issue: My generated test cases used a different format than what Testomat.io
   expects. I used:

   • headings for section dividers (category headers)

   • with YAML metadata blocks
   • Steps: and Expected Result: format
     But Testomat.io expects:

   • heading for suite title

   • directly followed by ## heading for test title
   • YAML metadata like type: manual, priority: critical on one line or proper block
     format
   • Simple text format without bold markup
2. Wrong directory: I initially created test cases in .testclaw-context/manual-tests/ which
   was already populated with 2500+ existing tests. When I tried to push, it tried to push ALL
   tests, causing the "Test IDs belong to another suite" error.
3. Hallucinated IDs: I generated test case IDs like @Tca91f1aa - which don't exist in
   Testomat.io format. The skill instructions say "NEVER generate Testomat.io test or suite
   IDs".
4. check-tests push issue: The CLI had trouble finding tests when run from a subdirectory.
   It required being in the project root and using specific file paths.
5. No --create flag initially: I forgot the --create flag which is needed to create new
   tests in Testomat.io.

Let me summarize these clearly.
[18.05.2026 02:50] Michael Bodnarchuk: Main Issues:

1. Test Format Mismatch

My generated format:

  ## Category Name                                                                          
                                                                                            
  <!-- test                                                                                 
  title: Test title                                                                         
  priority: critical                                                                        
  labels: [tag1, tag2]                                                                      
  -->                                                                                       
  Steps:                                                                                
  1. Do this                                                                                
  Expected Result:                                                                      
  It works                                                                                  

Expected Testomat.io format:

  <!-- suite                                                                                
  title: Suite Name                                                                         
  labels: tag1, tag2                                                                        
  -->                                                                                       
  # Suite Name                                                                              
                                                                                            
  <!-- test                                                                                 
  type: manual                                                                              
  priority: critical                                                                        
  labels: tag1, tag2                                                                        
  -->                                                                                       
  ## Test title                                                                             
                                                                                            
  Steps:                                                                                    
  1. Do this                                                                                

Fix: Follow existing .test.md files exactly — use ## for test titles directly after , no title: field, no bold markdown.
[18.05.2026 02:50] Michael Bodnarchuk: ### 2. Wrong Directory

Created test cases in .testclaw-context/manual-tests/ which had 2500+ existing tests. Push
attempted to sync ALL tests → "Test IDs belong to another suite" error.

Fix: Always create isolated directories for new test suites.

3. Hallucinated IDs

Generated fake IDs like @Tca91f1aa — the skill explicitly says "NEVER generate Testomat.io
test or suite IDs — they are server-generated."

Fix: Never include id: @t... or id: @s... in output.

4. CLI Navigation Issues

check-tests push couldn't find tests in subdirectories. Required being in project root +
explicit file path.

Fix: Copy single file to project root for push, then clean up.

5. Forgot --create flag

Without it, CLI wouldn't create new tests.

Fix: Always use --create --force flags for new suites.