Repository navigation
Make HTML the direct Markdown interchange - #1523
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
A shared Markdown codec can only replace third-party parsers safely once Markdown conversion has a direct, explicit HTML boundary. This also matches Intelligence/Data Machine content-format use and the HTML-first WordPress.com/Static Site Importer architecture.
Verification
composer testcomposer validate --strict --no-interactiongit diff --checkFollow-up
<->HTML codec.MarkdownAdaptercan consume it and remove Blocks Engine's direct League dependency graph without duplicating parser ownership.AI assistance disclosure: OpenAI gpt-5.6-sol via OpenCode inspected the cross-project architecture, refined the trackers, implemented and verified the change, and coordinated an attempted Homeboy Cook. Homeboy with OpenCode
openai/gpt-5.6-terravalidated provider readiness but failed before execution on component worktree resolution; Chris Huber authorized the direct local implementation and remains responsible for review.