[wfatih]

AsciiDocBackend collects paragraph lines in text_data and only adds them to the document at a blank line, a section header (#4428) or a literal block. When a list or a delimited table follows the text directly, the text stays pending and is added later, under whatever parent is current then:

Intro:          Before
* a             |===
* b             |a|b
                |===

On main the first input gives list[a, b, paragraph "Intro:"] and the Markdown - a\n- b\nIntro:, so the paragraph sits inside the list after its items. The second gives the table first and Before after it.

This flushes the pending text when a list starts (before the bold block title paragraph, which keeps the source order) and when a |=== table opens, in the same way the section header branch already does. Nothing changes when a blank line separates the text from the list or table, because the text is already flushed there.

Two new tests cover the list and the table case. Both fail on main and pass with this change. tests/test_backend_asciidoc.py passes (44 passed) and no groundtruth changes.

Checklist:

• Documentation has been updated, if necessary.
• Examples have been added, if necessary.
• Tests have been added, if necessary.

Review evidence:

• Before: Intro:\n* a\n* b exports as - a\n- b\nIntro: (the paragraph is a child of the list group). Before\n|===\n|a|b\n|=== exports the table before Before.
• After: Intro:\n\n- a\n- b, with the paragraph in the body before the list; Before comes before the table.
• pytest tests/test_backend_asciidoc.py: 44 passed. The new tests fail on main (2 failed, 42 passed).
• Groundtruth (tests/data/asciidoc/groundtruth/*) is unchanged.
• ruff check and ruff format --check pass on the changed files.

[github-actions]

✅ DCO Check Passed

Thanks @wfatih, all your commits are properly signed off. 🎉

[mergify]

Merge Protections

🟢 Merge protection satisfied — ready to merge.

Show 1 satisfied protection

🟢 Enforce conventional commit

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

• title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?(!)?:

[github-actions]

AI triage (advisory)

Checked commit ec62044264. The analysis read the diff only. It did not run code from this pull request.

This PR fixes AsciiDocBackend so that a pending paragraph is flushed before a list or a delimited table starts, preventing the paragraph from appearing inside the list or after the table. Two new focused tests cover both cases.

CI safety: no concern found. A maintainer must still approve CI.

3 related pull request(s) in the same code

PR	State	Signal	Assessment
#5045	open	changes the same code	related: PR #5045 fixes literal/listing block delimiters in the same backend file but does not address paragraph flushing before lists or tables.
#5010	open	changes the same code	related: PR #5010 fixes multi-line table row grouping in the same backend file but does not address paragraph flushing before a table opens.
#4428	merged	referenced as #4428	related: PR #4428 introduced the same _flush_text_data pattern at section headers (already merged); this PR extends it to list and table entry points.

_{The ai:* labels are advisory. They do not approve CI and they do not add tests:full. A new push runs this check again.}

[github-actions]

AI first review (advisory): no blocker found

This review covers the full diff at 0663f6edc9. It read the code and did not run it.

I found no defect. Both new flushes call _flush_text_data with the same parent that the neighbouring code uses for the next item. The two new tests assert the parent, the item order and the Markdown output, so they detect the original bug.

_{A maintainer makes the merge decision. This review never approves the pull request.}

[codecov]

Codecov Report

❌ Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
docling/backend/asciidoc_backend.py	0.00%	2 Missing ⚠️

📢 Thoughts on this report? Let us know!

[github-actions]

AI first review (advisory): no blocker found

This review covers the full diff at ec62044264. It read the code and did not run it.

I found no defect. Both new _flush_text_data calls use the same parent that the next item uses, so the pending paragraph is no longer added after the list or table. The text is flushed before the block-title paragraph, so source order stays correct.

_{A maintainer makes the merge decision. This review never approves the pull request.}