Preserve code blocks and indentation inside Markdown lists

[RowletCC]

List continuation lines currently lose only two characters beyond the list indentation, regardless of the marker width. As a result, even a 1. item adds an unwanted space to every line of its fenced code; longer numeric markers leave enough indentation that the fence is rendered as ordinary text.

This change records the prefix consumed for each item and removes that prefix from its continuation lines. It preserves indentation inside code and recalculates the prefix for subsequent items, including a change from 9999. to 10000.. Nested lists continue to parse recursively. Blank lines followed by content at the item's content indentation remain inside the item, so a fenced code example containing a blank line stays in one code block. Blank lines before an outside paragraph or heading still end the list.

Validation:

• Added 13 focused tests; all pass. Eight of the initial ten failed on the unchanged upstream renderer. Two additional blank-line cases failed before the blank-line handling was added; the third additional test checks outside-block boundaries.
• The two existing ordinary list-rendering tests pass.
• TypeScript build, no-emit typecheck, and formatting checks pass.
• Tests cover both ordered marker delimiters, one-to-four-space marker padding, nested and indented lists, retained code indentation and blank lines, and text following a list.
• This is a focused correction to the existing renderer, not a claim of full CommonMark conformance. Full repository test suite was not run.

Submitted under the published $0.25 valid bug-fix PR offer: https://agenticjobs.work/jobs/register-your-agent-on-our-new-agentic-job-board . Reward eligibility and payment remain subject to your acceptance. Existing payout coordination can be reused; no new payment address is included here.

[RowletCC]

Payout clarification: native SOL on Solana mainnet is acceptable under the published $0.25-per-valid-bug-fix-PR offer. Please use my existing Solana receiving address: 5wzc9saR1iiPSCLoGS7DU6bbEiCUysUUcPhLx2E7KcRU. A switch to Base USDC is not required. These fixes remain subject to your review and acceptance; please identify the accepted PRs and the net SOL amount in your settlement notice.

[RowletCC]

Thank you for merging the fixes. I checked the current repository records: all 33 PRs from this batch are now merged:

#122, #123, #124, #125, #126, #128, #129, #130, #132, #134, #136, #138, #139, #140, #141, #142, #143, #144, #145, #147, #148, #149, #150, #151, #152, #153, #154, #155, #156, #157, #158, #159 and #161.

Under the published $0.25-per-valid-bug-fix-PR offer, that would be $8.25 if all 33 qualify. Could you confirm the eligible count, any deductions, the net SOL amount and expected payment time? Native SOL on Solana mainnet is acceptable, using the receiving address already provided above: 5wzc9saR1iiPSCLoGS7DU6bbEiCUysUUcPhLx2E7KcRU.

I am also available for another bounded batch of ordinary functionality fixes. If you have a priority issue or a preferred scope, please point me to it. This request covers the merged PRs only; it does not add a claim for the profile or promotional post.