docs: define Phase 3 independent library program - #158
Open
ZSeanYves wants to merge 1 commit into
Open
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.
Change summary
Define Phase 3 as five separately initiated subphases: safezip, xml-stream, opc, pdf-extract, and the HTML/YAML/TOML shadow plus Markdown conformance evaluation.
Scope
Documentation-only update to docs/project-maintenance-plan.md. No library repository or implementation is created in this PR.
Risk and ownership
R0 documentation change. It establishes future R3 library, security, dependency, and release gates without changing current product behavior.
Contract and compatibility
Phase 0-2 behavior remains unchanged. Independent libraries must not depend on MarkItDown types; MarkItDown may consume only released versions through thin adapters and dual-run migration.
Verification
Checklist