fix: 🐛 Project structure creation with bare codeblocks is breaking markdown display and creation

[chezsmithy]

Description

Claude 4 sonnet is very excited about creating project structure display in readme files. When this was attempted the markdown display was broken and the file output was truncated. This was due file structure being outputted with nested codeblocks without a type attached.

When I orginally implemented a fix to this code I noted that there might be some risky edge cases where the nested code blocks didn't have types. As such this PR should solve for that use case by implementing a look ahead feature to check upcoming code blocks to determine if nesting is starting or we are ending the outer code block nesting early.

Checklist

• I've read the contributing guide
• The relevant docs, if any, have been updated or created
• The relevant tests, if any, have been updated or created

Screenshots

[ For visual changes, include screenshots. Screen recordings are particularly helpful, and appreciated! ]

Tests

[ What tests were added or updated to ensure the changes work as expected? ]

I've added a new function for the look ahead checking, and added new tests for that. Then I added a specfic test for the nested structure output that was failing.

---

Summary by cubic

Fixed an issue where project structure markdown with nested bare codeblocks would break display and truncate output.

• Bug Fixes
  • Added logic to detect and handle nested bare codeblocks without a type.
  • Updated tests to cover these edge cases.

[netlify]

👷 Deploy request for continuedev pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	a4e383a

[sestinj]

@chezsmithy There is a failing test, but I do like the PR. Will merge once tests are fixed

[chezsmithy]

TODO Items:

• Passing tests
• Review all ``` and STOP checking to make sure it is looking only for leading backticks or STOP keywords and not catching examples inside of code strings. Thus tests won't generate using these keywords or truncation can occur.
• Optimize lookahead function for ``` / STOP checking to not scan the whole remainder of the file if we can.